Repository navigation
Print zone-aware stack traces #130
Description
Activity
- added this to the milestone
on Nov 9, 2015 I'm not actively working on this specific thing, but the work I'm doing is teaching me what I need to know to be able to do it.
I know enough now to know that I didn't know enough when filing the bug.
- added a commit that references this issue
on Mar 21, 2019 This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Aug 17, 2021
Wednesday Aug 19, 2015 at 23:16 GMT
Originally opened as https://github.com/flutter/engine/issues/702
It's my understanding that when you use "async", zones keep track of the stack traces such that you can get sane usable stack traces. We should enable that by default in debug mode (at least).
CC @sethladd who may know what I'm talking about (since I don't...).