-
Notifications
You must be signed in to change notification settings - Fork 30k
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
inspector: crash on debugger connection if JS session is already active #16852
Comments
Seems to be a duplicate of #14745. Specifically #14745 (comment) |
This is a bug in the Node inspector code. There is an assertion thrown when WS session is connected while there's a JS bindings session. I tried to fix it in the past, but it requires a rework of the WS connection process that is currently happening on another thread but now will need a roundtrip to the main thread. Chrome is currently launching support for the multiple concurrent Inspector sessions. Once that support is stable and Node moves on a compatible V8, this assertion will be removed. There will likely be a need to do some other work in Node.js to support concurrent sessions - but at least this bug will be auto-fixed. |
I am still planning to take another look at this bug later this week, time permitting - I think there might be a reasonable fix. |
Attaching WS session will now include a roundtrip onto the main thread to make sure there is no other session (e.g. JS bindings) This change also required refactoring WS socket implementation to better support scenarios like this. Fixes: #16852 PR-URL: #17085 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Timothy Gu <timothygu99@gmail.com>
Attaching WS session will now include a roundtrip onto the main thread to make sure there is no other session (e.g. JS bindings) This change also required refactoring WS socket implementation to better support scenarios like this. Fixes: #16852 PR-URL: #17085 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Timothy Gu <timothygu99@gmail.com>
Node is wonderful, we get the opportunity to debug the debugger. |
Found this on googleapis/cloud-debug-nodejs#356 originally.
Crashes with:
This affects
master
,9.x
and8.x
./cc @nodejs/v8-inspector
The text was updated successfully, but these errors were encountered: