roryschadler opened a new issue, #374: URL: https://github.com/apache/pulsar-client-node/issues/374
I found that when I created and immediately closed readers a couple times in a row, the client would fail with a segfault. I'm not familiar with the C++ lib underpinning this client, but it appears to be due to the listener callback. Segfault stack: ```text PID 57514 received SIGSEGV for address: 0x10 0 segfault-handler.node 0x000000010624cef8 _ZL16segfault_handleriP9__siginfoPv + 296 1 libsystem_platform.dylib 0x0000000185537584 _sigtramp + 56 2 pulsar.node 0x0000000119e136a8 _Z19ReaderListenerProxyN4Napi3EnvENS_8FunctionEP23ReaderListenerProxyData + 92 3 pulsar.node 0x0000000119df41a8 _ZN4Napi18ThreadSafeFunction6CallJSEP10napi_env__P12napi_value__PvS5_ + 68 4 node 0x000000010095edc4 _ZN6v8impl12_GLOBAL__N_118ThreadSafeFunction7AsyncCbEP10uv_async_s + 440 5 node 0x000000010135d868 uv__async_io + 268 6 node 0x000000010136f940 uv__io_poll + 1020 7 node 0x000000010135de2c uv_run + 476 8 node 0x00000001008c1754 _ZN4node21SpinEventLoopInternalEPNS_11EnvironmentE + 256 9 node 0x00000001009ce63c _ZN4node16NodeMainInstance3RunEPNS_8ExitCodeEPNS_11EnvironmentE + 164 10 node 0x00000001009ce3d8 _ZN4node16NodeMainInstance3RunEv + 124 11 node 0x0000000100959494 _ZN4node5StartEiPPc + 776 12 dyld 0x000000018517e0e0 start + 2360 ``` (collected using https://www.npmjs.com/package/segfault-handler) I'm trying to set up a reproduction (the actual use case is a closed-source app). I don't have one yet, but I'm working on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
