search

ddopson / node-segfault-handler

Tool for debugging native Node.js modules and getting stack traces when things go wrong.
BSD 3-Clause "New" or "Revised" License
319 stars 74 forks source link

SIGSEGV in 0.0.64 #48

Closed nazar-pc closed 6 years ago

nazar-pc commented 6 years ago

There is still some memory-related issue which very rarely happens for me locally and sometimes on CI:

PID 16417 received SIGSEGV for address: 0x0
/web/github/detox-core/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x1b19)[0x7f8c20d34b19]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x13150)[0x7f8c2332e150]
node(_ZN2v86Object3GetENS_5LocalINS_5ValueEEE+0xa)[0xaf766a]
/web/github/detox-core/node_modules/wrtc/build/wrtc/v0.0.64/Release/node-v59-linux-x64/wrtc.node(_ZN11node_webrtc14PeerConnection3RunEP10uv_async_si+0x5a4)[0x7f8c201953a4]
node[0x1418ceb]
node[0x142abd8]
node(uv_run+0x156)[0x1419676]
node(_ZN4node5StartEP9uv_loop_siPKPKciS5_+0x4dd)[0x11fca6d]
node(_ZN4node5StartEiPPc+0x153)[0x11f93e3]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f8c22f5c1c1]
node[0x89c371]

I'm currently investigating where and why it happens.

nazar-pc commented 6 years ago

Wow, sorry, wrong repo O_o