You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
natebosch opened this issue
Apr 12, 2022
· 1 comment
Labels
area-error-messagingclosed-duplicateClosed in favor of an existing reportP1A high priority bug; for example, a single project is unusable or has many test failures
Sometimes unhandled async exceptions don't show up in the Console output area.
Steps to reproduce problem
The problem does not reproduce reliably. Refreshing the page seems to result in either having exceptions work, or not work. When they don't work they will be consistently suppressed on every run until the page is reloaded.
Additional info
Browser
Browser: Chrome
Version: 100.0.4896.75
Machine
Operating system: macOS Monterey
Version: 12.3.1
Your code
What code was in the editor, if any, when the failure occurred? You
can paste it in below:
voidmain() {
throw'sad';
}
DartPad's output
There is sometimes no output at all, or there is the expected output:
Uncaught Error: sad
In either case, the browser JS debugger console does show the error
Uncaught sad
at Object.wrapException (<anonymous>:356:17)
at <anonymous>:3101:23
at _wrapJsFunctionForAsync_closure.$protected (<anonymous>:2549:15)
at _wrapJsFunctionForAsync_closure.call$2 (<anonymous>:3484:12)
at Object._asyncStartSync (<anonymous>:2493:20)
at main (<anonymous>:3106:16)
at <anonymous>:4255:7
at <anonymous>:4238:7
at dartProgram (<anonymous>:4249:5)
at <anonymous>:4257:3
The text was updated successfully, but these errors were encountered:
area-error-messagingclosed-duplicateClosed in favor of an existing reportP1A high priority bug; for example, a single project is unusable or has many test failures
What happened?
Sometimes unhandled async exceptions don't show up in the Console output area.
Steps to reproduce problem
The problem does not reproduce reliably. Refreshing the page seems to result in either having exceptions work, or not work. When they don't work they will be consistently suppressed on every run until the page is reloaded.
Additional info
Browser
Browser: Chrome
Version: 100.0.4896.75
Machine
Operating system: macOS Monterey
Version: 12.3.1
Your code
What code was in the editor, if any, when the failure occurred? You
can paste it in below:
DartPad's output
There is sometimes no output at all, or there is the expected output:
In either case, the browser JS debugger console does show the error
The text was updated successfully, but these errors were encountered: