Open iposva-google opened 11 years ago
cc @a-siva.
The dart:async abstractions does come with a cost as the frames are dominated by dart:async code.
Looking at the bottom of the stack, then frames 65-57 and 55-47 are handling adding data to a sync StreamController. When there is a listener and the stream is not paused this is a direct call to the listener. This should be the normal case when processing a HTTP request. Maybe some of these call paths can be optimized.
This is a bug-tracker, not stack-overflow. Rewriting the summary.
Changed the title to: "handleMessage in HttpClient goes through too many (zone/async) redirections".
Removed Type-Defect label. Added Type-Enhancement, Library-Async labels.
I think we've improved stack traces for async stuff.
Will we reasonably take any action on this? Can it be closed @lrhn ?
Looked at some random error from a flaky test. The answer is about 60 frames too many: