-
Notifications
You must be signed in to change notification settings - Fork 69
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
Application intermittent crashed with SIGSEGV signal. #47
Comments
Today I've got one more crash with the same trace:
|
I've change my ping function code and got another result. In this case I've got SIGAB:
And the following errors in stderr:
Changed ping function:
|
Hi, I've am quite busy with work at the moment which is why I haven't be able to look at this properly yet. Until I do the only thing I can advise at this point is that I have seen similar issues in the past when the session.close() is called multiple times. Apologies Steve |
@stephenwvickers , thanks for an advice. Thanks, Roman. |
The way it is supposed to be used is by creating a session once and then using to do all your ping work, I.e. never close it just keep using it. |
Thank you Steve, I'll remove all session.close and try whether it helps. |
Hello,
I use net-ping 1.2.1(node-raw-socket 1.6.0) in my app with node 8 on Debian based system.
I found out that from time to time my node app crashes with SIGSEGV and generates core file.
I tried to check it, but don't have much experience in that.
But it looks like crashes related to the node-raw-socket, because it crashes right after performing something related to the node-raw-socket.
Here is llnode stack trace:
0x00007f94c38f00bc raw.node`raw::SocketWrap::HandleIOEvent(int, int) + 508
JS ping closure function:
The text was updated successfully, but these errors were encountered: