Anakun

I can confirm it still segfault. I will investigate with gdb and tell you whats the new trace.

Hey @Brooooooklyn sorry! I had an other local dependency I forgot to change. I pushed to the same branch again for the repo "unit-test-framework". It should work now, please run...

I collected the backtrace on NAPI3: ``` Thread 19 "node" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffe87fff700 (LWP 1707879)] 0x0000000001363f23 in v8::internal::GlobalHandles::Destroy(unsigned long*) () (gdb) bt #0 0x0000000001363f23...

Hey @Brooooooklyn. Thanks for this patch about errors. I have a working branch that you can try: Switch to: op-vm -> error/fix-napi3-error-handling unit-test-framework -> napi3-fix-test I noticed that switching from...

> [@BlobMaster41](https://github.com/BlobMaster41) If you don't want the `ThreadsafeFunction` block your program, you can declare the `ThreadsafeFunction` as `Weak`, change the `Weak` to `true` here: > >  > > >...

Could it be caused because we are using it in worker threads?

Hey @Brooooooklyn, for the segfault, it happens on my pc and my servers that use way different cpu, im on intel and my servers are on different amd versions. To...

@Brooooooklyn Whats the next step from here? I need worker threads..

Ok I tried some stuff out and I noticed that if I change everything from Buffer to Uint8Array, it does not segfault but node js crash instead. ``` # #...

Even converting everything to strings and attempting to send string from node js to napi and string from napi to node js result in a fatal segfault after a while.