Open wd021 opened 2 years ago
Have you seen this recently?
The bug in #145 is different than the stack you posted. I also reproduced this here too
PID 16063 received SIGSEGV for address: 0x3871f8cfb9c8
0 segfault-handler.node 0x0000000105545354 _ZL16segfault_handleriP9__siginfoPv + 288
1 libsystem_platform.dylib 0x00000001bbbec4e4 _sigtramp + 56
2 ironfish-rust-nodejs.darwin-arm64.n 0x000000011304119c _ZN4napi15bindgen_runtime15module_register9custom_gc17h6d3b57ee2491e70eE + 28
3 ironfish-rust-nodejs.darwin-arm64.n 0x000000011304119c _ZN4napi15bindgen_runtime15module_register9custom_gc17h6d3b57ee2491e70eE + 28
4 node 0x0000000100509524 _ZN6v8impl12_GLOBAL__N_118ThreadSafeFunction7AsyncCbEP10uv_async_s + 432
5 node 0x0000000100e484c4 uv__async_io + 320
6 node 0x0000000100e5a210 uv__io_poll + 1036
7 node 0x0000000100e48954 uv_run + 380
8 node 0x00000001004816d4 _ZN4node13SpinEventLoopEPNS_11EnvironmentE + 244
9 node 0x00000001005cc280 _ZN4node6worker6Worker3RunEv + 1600
10 node 0x00000001005cefe4 _ZZN4node6worker6Worker11StartThreadERKN2v820FunctionCallbackInfoINS2_5ValueEEEEN3$_38__invokeEPv + 56
11 libsystem_pthread.dylib 0x00000001bbbd5240 _pthread_start + 148
12 libsystem_pthread.dylib 0x00000001bbbd0024 thread_start + 8
zsh: segmentation fault ironfish start
What happened?
@NullSoldier reported this same bug last year https://github.com/iron-fish/ironfish/issues/145. At the time, we were using SimplePeer for webrtc communication. This PR https://github.com/iron-fish/ironfish/pull/144 fixed the issue by replacing SimplePeer with an ironfish forked version.
We've since moved to node-datachannel and it seems like we're seeing this bug again with the
onMessage
callback in the data channel wrapper, https://github.com/murat-dogan/node-datachannel/blob/1875484cc7d6737f59407e4f15aabe119984a0e8/src/data-channel-wrapper.cpp#L396-L435.Version
0.1.36
Debug output
No response
Relevant log output
Graffiti
wd021