Comment #1 on issue 3545 by [email protected]: Frequent SEGV crashes in
nodejs
https://code.google.com/p/v8/issues/detail?id=3545
After further investigation:
node-0.10.26 ostensibly uses the same v8 version, and crashes merely once
every few days. So it could be something else in the binary corrupting
memory that happens to be used by v8, or it could be that different v8 code
paths are being exercised in the new version of node.
I've found that neither the official nodejs binaries or fedora's packaged
versions of the same node version exhibit this problem. After figuring that
out, I narrowed down the important difference to the
`-fstack-protector-strong` GCC option. Specifically, if I do:
export CFLAGS='-fstack-protector-strong'
before building the vanilla nodejs sources, then the segfaults no longer
happen. This seems like more of a fortunate side effect than a fix, but
perhaps it can help someone more knowledgeable reproduce the issue.
(this is all on stock fedora 20 with gcc (GCC) 4.8.3 20140624 (Red Hat
4.8.3-1))
I also found that building node in debug mode (to possibly show more of
those stack lines) eliminates the problem too, so it doesn't look like I'll
be able to get a better stacktrace unfortunately.
Please let me know if you think it's a nodejs issue, and I'll punt it
elsewhere. I originally figured it was v8 simply because that's the only
thing I could find in the backtrace, but now I'm not so sure.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
