cc @tomball.

This comment was originally written by @tomyeh

+1 Global exception handling is important for asynchronous programming. However, the more challenging one is how to carry the context to the handler. For example, if the exception happens when serving a HTTP request, we have to close the connection in the handler.

Not sure there is an elegant way for doing it. Future.catchError is a good solution, thought not global. But, to apply it, it means Stream, Timer and all async invokers have to implement catchError.

Issue #8417 has been merged into this issue.

cc @sigmundch.
cc @jmesserly.
cc @gbracha.

Issue #9273 has some details on work that happened to enable the VM to do this.

Set owner to @floitschG.
Added C1 label.

Removed Priority-Medium label.
Added Priority-High label.

Probably won't make it into M5, but until then we should have a way to capture uncaught exceptions in a scoped way. You could then just put this into the main.

Added this to the M6 milestone.

Removed this from the M6 milestone.
Added this to the M7 milestone.

Removed this from the M7 milestone.
Added this to the M8 milestone.

Any updates on this?

If I'm not wrong this should now be possible by wrapping the code in main into a zone.

Lowering priorit, but not closing yet, since we are investigating other means to make top-level errors non-fatal.

Removed Priority-High label.
Added Priority-Medium label.

Removed this from the M8 milestone.
Added this to the 1.6 milestone.

Removed this from the 1.6 milestone.
Added Oldschool-Milestone-1.6 label.

Removed Oldschool-Milestone-1.6 label.

We now have Isolate.current.addErrorListener and Isolate.current.setErrorsFatal along with the Zone based solutions.