Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Debian9: Assertion `thread_id_key != 0x7777' failed #451

Open
ygaeon opened this issue Apr 28, 2021 · 2 comments
Open

Debian9: Assertion `thread_id_key != 0x7777' failed #451

ygaeon opened this issue Apr 28, 2021 · 2 comments

Comments

@ygaeon
Copy link

ygaeon commented Apr 28, 2021

  • node 16.0.0
  • npm 7.10
  • node-gyp 8.0.0
  • debian 9 stretch Debian 4.9.189-3+deb9u2
node: ../src/coroutine.cc:145: void* find_thread_id_key(void*): Assertion `thread_id_key != 0x7777' failed.
Aborted

I added a few outputs to try to debug this myself but I couldn't figure it out further and reach out here.

node_modules/fibers$ node fibers
ii: 1 coro_thread_key: 6: tls (-1946153776) != thread_id (2)
ii: 2 coro_thread_key: 6: tls (0) != thread_id (2)
ii: 3 coro_thread_key: 6: tls (0) != thread_id (2)
ii: 4 coro_thread_key: 6: tls (0) != thread_id (2)
ii: 5 coro_thread_key: 6: tls (0) != thread_id (2)
isolate_key: 0
thread_data_key: 0x1
thread_id_key: 0x7777
node: ../src/coroutine.cc:145: void* find_thread_id_key(void*): Assertion `thread_id_key != 0x7777' failed.
Aborted
@laverdet
Copy link
Owner

There's a note on the front page README about this. Fibers will not be supported on nodejs v16.x or higher.

@ygaeon
Copy link
Author

ygaeon commented Apr 28, 2021 •
edited
Loading

OK ... re-reading ... true true ... missed that, sorry.

Edit: Closing

@GregOriol GregOriol mentioned this issue Apr 29, 2021
Closed
4 tasks
This was referenced Apr 29, 2021
Closed
Closed
@hyacinthus hyacinthus mentioned this issue May 8, 2021
Closed
@kyletsang kyletsang mentioned this issue May 9, 2021
Merged
This was referenced Jun 8, 2021
Open
Closed
@4-l-Clover 4-l-Clover mentioned this issue Sep 3, 2021
Closed
4 tasks
@quiram quiram mentioned this issue Sep 9, 2021
Open
@dustinmichels dustinmichels mentioned this issue Oct 7, 2021
Closed
RhysXia pushed a commit to xl-vision/xl-vision that referenced this issue Oct 15, 2021
build: remove fibers to support node version above 16
468ef6f 
laverdet/node-fibers#451
jtlindsey added a commit to jtlindsey/nuxtjs.org that referenced this issue Dec 15, 2021
@jtlindsey
Remove fibers dependency recommendation
796ebbb 
As of April 2021 maintainers of `fibers` announced it does not work with the current LTS version of Node (16.x) and "[recommends you avoid its use if possible](https://github.com/laverdet/node-fibers/blob/8f2809869cc92c28c92880c4a38317ae3dbe654d/README.md?plain=1#L1)". The authors README.md commit titled "[the end](laverdet/node-fibers@8f28098)" along with the verbiage "inevitable that one day this library will abruptly stop working and no one will be able to do anything about it" suggest this package will not be maintained going forward.

Other benefits of the change:
- Bring this page into alignment with [The Nuxt Configuration Guide](https://nuxtjs.org/docs/features/configuration/) which does not suggest users install fibers.
- Reduce [startup headaches](laverdet/node-fibers#451) for users creating new projects using the latest LTS version of node.
@jtlindsey jtlindsey mentioned this issue Dec 15, 2021
Merged
@tuchang tuchang mentioned this issue Feb 9, 2022
Open
RhysXia pushed a commit to xl-vision/xl-vision that referenced this issue Feb 15, 2022
build: remove fibers to support node version above 16
0d76d2e 
laverdet/node-fibers#451
RhysXia added a commit to xl-vision/xl-vision that referenced this issue Feb 15, 2022
@RhysXia
build: remove fibers to support node version above 16
9a6bbfe 
laverdet/node-fibers#451
@cloudfreexiao cloudfreexiao mentioned this issue Apr 16, 2022
Closed
@mattheath mattheath mentioned this issue Jul 26, 2022
Open
@heapifyman heapifyman mentioned this issue Nov 12, 2022
Closed
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@laverdet @ygaeon