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
If the Chrome debugger is paused on a line with an await operator and you step over the next function call (F10), then the debugger does not pause in the next line, but jumps to the end of the current function.
Reproduction:
Launch the unit test below.
Open the debugger URL in Chrome: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:4242/debug
Advance the debugger until you end up in line 3: const result = await compute();
Use the Step over next function call button or press F10.
Before:
After "Step over":
As a user, you would expect the debugger to pause in line 4, as it is also the case if you run the same scripts in Chrome natively.
For completeness, this is the DevTools protocol log: ProtocolMonitor-20230420T154826.json.log
If the Chrome debugger is paused on a line with an
await
operator and you step over the next function call (F10), then the debugger does not pause in the next line, but jumps to the end of the current function.Reproduction:
devtools://devtools/bundled/js_app.html?ws=127.0.0.1:4242/debug
const result = await compute();
Before:
After "Step over":
As a user, you would expect the debugger to pause in line 4, as it is also the case if you run the same scripts in Chrome natively.
For completeness, this is the DevTools protocol log: ProtocolMonitor-20230420T154826.json.log
Tested with GraalVM 22.3.1 on Java 17.
Test:
The text was updated successfully, but these errors were encountered: