Introduce hooks for providing context for engine crashes #33617
Labels
a: debugging
Debugging, breakpoints, expression evaluation
dependency: dart
Dart team may need to help us
engine
flutter/engine repository. See also e: labels.
P2
Important issues not at the top of the work list
team-engine
Owned by Engine team
triaged-engine
Triaged by Engine team
Internal: b/133849502
Our clients are reporting that engine crashes are hard to diagnose and reproduce. One of the most common complaints is the lack of context around an engine crash (which page did the app crash on? which experiment flags were turned on? etc).
Is it possible to provide a callback to the framework when the engine is crashing? Something like Java's UncaughtExceptionHandler.
The alternative is to ask apps to keep logging messages and scan the log to find the last one before crash. This is error-prone, cumbersome and not accurate.
The text was updated successfully, but these errors were encountered: