-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
vm module regression #53346
Comments
Sorry, wrong PR to link |
This reverts commit d1f18b0. Closes: nodejs#53346
Thanks for the report. I don't have the capacity to investigate and fix this, so I opened a revert PR. |
On a side note the stack trace looks a bit weird and I think this is similar to the incorrect backtrace I saw in #50849 (comment) cc @legendecas |
@joyeecheung thanks for the ping. I can reproduce the stack trace with the nightly build on Windows but can not reproduce the stack trace with a local build. I'll take a look at it. |
This reverts commit d1f18b0. Closes: nodejs#53346 PR-URL: nodejs#53348 Fixes: nodejs#53346 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Vinícius Lourenço Claro Cardoso <contact@viniciusl.com.br>
This reverts commit d1f18b0. Closes: nodejs#53346 PR-URL: nodejs#53348 Fixes: nodejs#53346 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Vinícius Lourenço Claro Cardoso <contact@viniciusl.com.br>
Version
v23.0.0-nightly20240605b26a260ce5
Platform
windows
Subsystem
vm
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
Additional information
I believe #53172 is the cause.
The text was updated successfully, but these errors were encountered: