-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using the Node.js inspector can lead to a crash #103
Comments
Possible workarounds:
This bug impacts only stepping over the loop with a debugger - it does not happen in any other case |
Suspected to be related to the double throw coming from Node-API |
Another workaround is to simply set up a manual breakpoint in the iterator on this line (the line that throws when the end of the iterable is reached): Line 28 in 978e087
Once this breakpoint has been triggered, the V8 debugger will correctly identify the source of the exception and won't crash - even if the breakpoint is removed. |
When using the Node.js inspector to step over the final iteration of a loop iterating over a Python iterable, when Python throws the final exception, V8 crashes.
Seems to happen only in async contexts.
The crash is caused by V8 unable to identify the correct handler to step over.
The text was updated successfully, but these errors were encountered: