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
I am using node::CommonEnvironmentSetup::Create to create multiple JS virtual machine instances, each running in a different thread. However, I'm encountering difficulties with debugging.
Node.js seems to only allow a single inspector instance. If I pass kOwnsInspector (or kDefaultFlags) for each CommonEnvironmentSetup::Create, the second CommonEnvironmentSetup::Create call throws an exception, which seems to be due to an IO thread initialization conflict.
If only the first CommonEnvironmentSetup::Create has kOwnsInspector, subsequent calls to CommonEnvironmentSetup::Create fail to create an inspector because they attempt to use the same listening port. I have not found any public API that allows modifying the listening port.
Lastly, I experimented with passing a parent_handle, but it seems that the debugger cannot reach the non-primary instances during debugging.
Is there a way to debug multiple JS virtual machine instances running in different threads?
Minimal Reproduction
No response
Output
No response
Before You Submit
I have looked for issues that already exist before submitting this
Node.js Version
v23.0.0-pre
NPM Version
10.6.0
Operating System
windows
Subsystem
Other
Description
I am using node::CommonEnvironmentSetup::Create to create multiple JS virtual machine instances, each running in a different thread. However, I'm encountering difficulties with debugging.
Node.js seems to only allow a single inspector instance. If I pass kOwnsInspector (or kDefaultFlags) for each CommonEnvironmentSetup::Create, the second CommonEnvironmentSetup::Create call throws an exception, which seems to be due to an IO thread initialization conflict.
If only the first CommonEnvironmentSetup::Create has kOwnsInspector, subsequent calls to CommonEnvironmentSetup::Create fail to create an inspector because they attempt to use the same listening port. I have not found any public API that allows modifying the listening port.
Lastly, I experimented with passing a parent_handle, but it seems that the debugger cannot reach the non-primary instances during debugging.
Is there a way to debug multiple JS virtual machine instances running in different threads?
Minimal Reproduction
No response
Output
No response
Before You Submit
The text was updated successfully, but these errors were encountered: