-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Segmentation fault on v8.1.3 #14069
Comments
@stefanosala Can you post the output of |
Thanks @bnoordhuis for looking into the issue!
Here's the Here's the
Removing all compiled modules doesn't make any difference either. Thanks! |
Could you isolate the function that triggers this bug? |
Thanks. Looks like Can you try a debug build and see what happens? Is there an easy way for us to reproduce? |
But just to be sure: what does |
@targos here's the JS stack trace: https://gist.github.com/stefanosala/1345fa59d02a77f89531eca059f0d03c |
@bnoordhuis I'll try compiling a debug version. |
@bnoordhuis it prints:
|
@stefanosala What about simply I'd delete that gist again if I were you, it contains sensitive information. |
@bnoordhuis thanks, deleted.
|
Hi @bnoordhuis,
Do you need anything else? |
@stefanosala Thanks. Can you check in gdb what If you have the time and inclination, it would be helpful to know if you also experience the issue with the master branch which bundles a newer V8 version. If it's fixed there, we can look into isolating and back-porting the fix. |
@bnoordhuis the issue is not present building from master.
I'm not sure how to do that, I'm sorry :( |
In gdb, type |
Thanks, here you are:
|
Thanks. I had a working hypothesis but seeing SpeculativeNumberDivide in there sadly invalidated it. :-) It's interesting that you didn't see the issue with V8 5.9 because I don't think this particular code path changed much since 5.8. @bmeurer Perhaps you have a suggestion? |
Is there some kind of asm.js code involved? I'm a bit puzzled about the stack trace. |
Nope @bmeurer, no asm.js involved in the project :( |
Can you check with the latest Node Canary? cc @mathiasbynens @schuay @nodejs/v8 |
@bmeurer not happening on canary |
Can you also try with Node 8.2.0RC1 please? |
No issue on 8.2.0RC1 .... /shrug :) |
Ok, thanks. @targos do we also have downloadable Node w/ V8 6.0? |
I don't think so. But if 5.9 doesn't have the issue, do we need to check 6.0? |
Oh, right, sorry. I was confused. |
I guess everything will be magically fixed on 8.2 then? 👯 :) |
I don't follow the above - it's totally out of my league! - but if it helps, I've observed the following:
<SNIP>
npm WARN enoent ENOENT: no such file or directory, open '/package.json'
npm WARN !invalid#1 No description
npm WARN !invalid#1 No repository field.
npm WARN !invalid#1 No README data
npm WARN !invalid#1 No license field.
+ [email protected]
added 115 packages in 7.118s
npm info ok
Segmentation fault |
Hey folks, wait a min... I tried with 8.2.1 and the issue is still there :( |
#14004 landed and will be released in v8.3.0. I'll close this out, cheers. |
Hi there,
we noticed that we're receiving a Segmentation Fault on node v8.
Here's the backtrace:
Here's a list of compiled modules:
We tried to downgrade to latest v7 and the issue is not there, so it must be something with node-v8.
Thanks!
Stefano
The text was updated successfully, but these errors were encountered: