@u4/opencv4nodejs cannot be used in worker threads

[mf-mitchelrydzynski]

Environment

• opencv4nodejs: 6.5.2
• openvc: 4.9.0
• nodejs: 18.16.1
• macos: sonoma 14.4.1

Description of Issue

I'm attempting to offload image processing to workers using the native worker_threads library. The first time my application starts up a worker, runs the computation, and cleans up the worker, things work great. However, the second attempt to do so causes my whole app to crash silently. I noticed that commenting out any imports of @u4/opencv4nodejs in the worker files allows them to start and terminate as often as I like without issue. Upon investigating, I found the below resources related to context aware c++ addons.

Additional Resources

• opencv4nodejs inside worker threads justadudewhohacks/opencv4nodejs#555 - same open issue in the upstream repo
• requiring C++ addon modules occurs 'Error: Module did not self-register.' with Worker Threads nodejs/node#21481 - closed issue in nodejs further describing the problem
• https://nodejs.org/docs/latest-v10.x/api/addons.html#addons_context_aware_addons - relevant nodejs documentation
• Module did not self-register error when using Electron #43 - open issue in this library, same fundamental problem showing up there because electron runs multiple node instances

Given the computationally intensive nature of image processing, supporting workers in order to not block the main thread seems like it should be a requirement for this library. Creating a long running subprocess is not an option for me due to memory constraints. Happy to provide any more info/help land on a solution. Thanks!

[stoefln]

Any news on this? Electron.js also dropped support for non-context-aware models, so I don't think opencv4nodejs can still run on current electron versions.

[rambo-panda]

Same question ！！ hope to support, after all, imwrite blocking is too long

#148