-
Notifications
You must be signed in to change notification settings - Fork 364
Open
Labels
P1high priority issues at the top of the work list, actively being worked on.high priority issues at the top of the work list, actively being worked on.dart2wasm
Description
I noticed that if I explicitly trigger a RangeError when we setup our analytics (in _analytics_web.dart), it crashes our dart2wasm-compiled app, but not our dart2js app.
Need to investigate more, might be related to this comment here:
devtools/packages/devtools_app/lib/src/shared/framework/app_error_handling.dart
Lines 60 to 66 in 77e37d7
| (Object error, StackTrace stack) { | |
| // TODO(https://github.com/flutter/devtools/issues/7856): can we detect | |
| // severe errors here that are related to dart2wasm? Otherwise we may | |
| // crash DevTools for the user without any way for them to force reload | |
| // with JS. | |
| reportError(error, stack: stack, errorType: 'zoneGuarded'); | |
| throw error; |
Metadata
Metadata
Assignees
Labels
P1high priority issues at the top of the work list, actively being worked on.high priority issues at the top of the work list, actively being worked on.dart2wasm