-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
An error occurred while running vm with breakOnSignt option in multiple worker_threads #43699
Comments
VoltrexKeyva
added
vm
Issues and PRs related to the vm subsystem.
worker
Issues and PRs related to Worker support.
labels
Jul 6, 2022
I think because modifying the
The operation as follows will trigger the bug:
I modify the code to verify this.
It works. |
4 tasks
nodejs-github-bot
pushed a commit
that referenced
this issue
Jul 14, 2022
PR-URL: #43780 Fixes: #43699 Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
4 tasks
danielleadams
pushed a commit
that referenced
this issue
Jul 26, 2022
PR-URL: #43780 Fixes: #43699 Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
targos
pushed a commit
that referenced
this issue
Jul 31, 2022
PR-URL: #43780 Fixes: #43699 Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
targos
pushed a commit
that referenced
this issue
Jul 31, 2022
PR-URL: #43780 Fixes: #43699 Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Oct 10, 2022
PR-URL: nodejs/node#43780 Fixes: nodejs/node#43699 Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
12 / 14 / 16 / 18 and current LTS
Platform
all
Subsystem
vm
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Always
What do you see instead?
The text was updated successfully, but these errors were encountered: