-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opencv4nodejs inside worker threads #555
Comments
Changing the module definition, as explained in the documentation, in -NODE_MODULE(opencv4nodejs, init)
+NODE_MODULE_INIT() {
+ init(exports);
+} as it will fail at runtime:
This seems to be a bigger change :( |
Yea, having the same problem myself. Trying to offload some image processing outside my main loop and transfer the opencv image to another worker / core. Ran into the same thing as I am trying to implement this. I don't have time to work on the opencv4nodejs project, so giving a +1 vote for solutions here. |
Hi, @justadudewhohacks. Any idea about this issue? I also tried to use Thank you! |
i just started my "worker" script as a child process (spawn) and it seems to work fine now. I just use the stdin and stdout, parse the in and out as JSON so it behaves the same as the "native workers". UPDATE : |
No updates yet? |
I'm also having this issue |
Using
opencv4nodejs
inside a worker thread causes the error messageModule did not self-register
.To make it work the module must be context aware as described here.
To reproduce the little snippet below (which is based on this bug report) can be used:
The text was updated successfully, but these errors were encountered: