Uncaught Error: Module did not self-register #26

Somebi · 2019-03-01T13:49:25Z

Getting this error... removing node_modules or npm rebuild is not helping.
This error is thrown when i'm using threads (workers)

mscdex · 2019-03-01T15:17:00Z

Node version?

mscdex · 2019-03-01T15:27:23Z

node addons have to explicitly support workers for them to work in that scenario. The main reason for this is that some addons can have global state which would not work for multiple threads.

Somebi · 2019-03-03T08:14:09Z

V10.10 don't remember for sure. пт, 1 мар. 2019 г., 17:27 mscdex <notifications@github.com>:

…

node addons have to explicitly support workers for them to work in that scenario. The main reason for this is that some addons can have global state which would not work for multiple threads. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAc7oaI6KkJryXwxystvT-bulHkHbMdmks5vSUbbgaJpZM4bZDHs> .

Somebi · 2019-03-03T08:16:04Z

But calling require not in the global scope, works without errors. Problem exists only when define module in the top most place (i.e. global scope) вс, 3 мар. 2019 г., 10:13 Denis Abramov <somebi@gmail.com>:

…

V10.10 don't remember for sure. пт, 1 мар. 2019 г., 17:27 mscdex ***@***.***>: > node addons have to explicitly support workers for them to work in that > scenario. The main reason for this is that some addons can have global > state which would not work for multiple threads. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#26 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAc7oaI6KkJryXwxystvT-bulHkHbMdmks5vSUbbgaJpZM4bZDHs> > . >

mscdex · 2019-03-03T08:43:26Z

Can you show an example of each?

migolovanov · 2019-08-22T11:01:52Z

I have meet same issue when tried to require xxhash in thread (node v12.8.1, pull/30 applied). But was able to solve it by changing src/hash.cc:

11c11,13
< NODE_MODULE(addon, Init);
---
> NODE_MODULE_INIT() {
>   Init(exports);
> }

and re-build binary: cd build && make

Code to reproduce the issue:

(async () => {
  const { job, start, stop } = require('microjob');
  var XXHash = require('xxhash')
  await start();
  await job(() => {
      var XXHash = require('xxhash')
  })
})()

yuche linked a pull request Aug 5, 2020 that will close this issue

Support worker thread, fix #26 #36

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uncaught Error: Module did not self-register #26

Uncaught Error: Module did not self-register #26

Somebi commented Mar 1, 2019

mscdex commented Mar 1, 2019

mscdex commented Mar 1, 2019 •

edited

Loading

Somebi commented Mar 3, 2019 via email

Somebi commented Mar 3, 2019 via email

mscdex commented Mar 3, 2019 •

edited

Loading

migolovanov commented Aug 22, 2019 •

edited

Loading

Uncaught Error: Module did not self-register #26

Uncaught Error: Module did not self-register #26

Comments

Somebi commented Mar 1, 2019

mscdex commented Mar 1, 2019

mscdex commented Mar 1, 2019 • edited Loading

Somebi commented Mar 3, 2019 via email

Somebi commented Mar 3, 2019 via email

mscdex commented Mar 3, 2019 • edited Loading

migolovanov commented Aug 22, 2019 • edited Loading

mscdex commented Mar 1, 2019 •

edited

Loading

mscdex commented Mar 3, 2019 •

edited

Loading

migolovanov commented Aug 22, 2019 •

edited

Loading