Why is the script killed by SIGSEGV?

Question

Node.js

Hello!
I have a Node js script. The script is small, nothing complicated, counts online via socket.io and issues counters to the client like how many users are on the site. All. 200 lines of code. Today the site received good traffic, online reached 1k, that is, more than 1k socket connections, this script fell sharply due to the error error: Forever detected script was killed by signal: SIGSEGV, it is unrealistic to raise. I even removed all the code, I just tried to include it and display console.log("hi"), it immediately crashes, I included the segfault-handler library to debug the error. Below I will show what it produces. At the same time, another script works in parallel, which is 5k lines of code more complex, but there are 100-200 online, and it also starts to fall because of this. I associate the error with a large load, but I can not understand the specific problem. The library gives a more specific error:

NodeSegfaultHandlerNative: about to dereference NULL (will cause a SIGSEGV)
PID 3759 received SIGSEGV for address: 0x1
/bot/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x2ca1)[0x7f10fe211ca1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7f11007d18d0]
/bot/node_modules/segfault-handler/build/Release/segfault-handler.node(_Z22segfault_stack_frame_1v+0x24)[0x7f10fe2120b4]
/bot/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x23b6)[0x7f10fe2113b6]
/root/.nvm/versions/node/v6.0.0/bin/node(_ZN2v88internal25FunctionCallbackArguments4CallEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEE+0xe1)[0x937b01]
/root/.nvm/versions/node/v6.0.0/bin/node[0x98b90b]
/root/.nvm/versions/node/v6.0.0/bin/node[0x98beb1]
[0x21a93b80961b]

I would be grateful for any help, advice. Maybe someone had a similar experience.