-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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 segmentation fault #27637
Comments
Stack trace:
/cc @nodejs/v8-inspector |
I can't reproduce this with master on MacOS. I can reproduce this with v12.14.0 though. EDIT: this seems intermittent, I can reproduce it after several tries. However it does not seem to reproduce if I use the |
Suspicios line in stack trace: |
I'm not sure this is the same issue or not, but I'm also experiencing segfaults when trying to inspect node with Chrome.
Cli:
It is necessary for the class Node version: v20.2.0 Please let me know if you'd like me to make a separate issue. |
I cannot reproduce on MacOS on node 20.9, maybe has been fixed, can you confirm @mik-jozef @Hakerh400 |
I can still reproduce with Node v20.5.1 and Ubuntu 22.04.3 LTS. Attaching a core dump (renamed from |
The original test case seems to be fixed. Tested on Windows 10 and Ubuntu 22.04: Reproduces in v18.9.1 Probably fixed in #44741 Unable to reproduce #27637 (comment) |
As @user7230724 said I can confirm that this seemed to get fixed in v19 and it's still fixed as of v23: So I think that this issue could safely be closed 🙂 |
Accessing
this
in static class field initialization context in some conditions crashes the process. This seems to be related both to Node.js inspector and Chrome devtool inspector.Here is an automated repro:
Save as
main.js
, then runnode main.js
Output:
The text was updated successfully, but these errors were encountered: