-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Assertion failed ../deps/uv/src/unix/stream.c, line 1563 #8258
Comments
It sounds like memory corruption. Nine times out of ten it's caused by a wayward native module (e.g. leveldown) so try excluding those first. You can try running it under valgrind and see if it complains. |
valgrind gives me the following output, which i cannot really make sense of or infer the causing package:
|
Run node directly under valgrind, you're tracing your shell now. Maybe try it on Linux as well. Valgrind is sometimes hit-and-miss on OS X. |
Ah! Here is the output on OS X: Indeed leveldb is among the dump in the heap summery. Does this mean the problems are most likely caused by it?
|
The leveldb entries are memory leaks, which makes sense - the program is terminated so leveldb doesn't get a chance to clean up. Still, it would be good to exclude it just to see if the problem goes away. Are you using the homebrew build by any chance? Someone reported a similar issue yesterday that went away when they switched to the official binaries from https://nodejs.org/. |
This issue has been inactive for sufficiently long that it seems like perhaps it should be closed. Feel free to re-open (or leave a comment requesting that it be re-opened) if you disagree. I'm just tidying up and not acting on a super-strong opinion or anything like that. |
@Trott having this issue in Connormiha/jest-css-modules-transform#14 |
@xumix If you can reproduce with a supported version of Node.js and your script doesn't use native modules, then please open a new issue and include steps to reproduce. The more minimal the test case, the better. |
Randomly just hit this or something similar myself. Using node v14.13.0 and npm v6.14.8 on macOS 10.15.7 (19H2). Assertion failed: (handle->type == UV_TCP || handle->type == UV_TTY || handle->type == UV_NAMED_PIPE), function uv___stream_fd, file ../deps/uv/src/unix/stream.c, line 1622.
[1] 47500 abort DEBUG=true PORT=9000 ./node_modules/.bin/qq ./src/schemas |
I was running into this today quite often. I updated my OSX software yesterday and the developer tools as well. NVM Node v18.14 |
I'd also had the same error, across multiple node versions from v18 to v22
The fix for me was: I'd installed An alternative would've been to just not use the |
I cannot really provide reproducible code since this error happens in a non deterministically but here some details:
Tested on node v6.4.0/ 6.3.1/ 6.2.2
On Linux machines the same code is causing the message "segmentation fault" (also not deterministically).
I'm using https://github.com/Level/leveldown package which might cause this error since it sometimes happens on reading/writing from the db, but also on totally unrelated function calls.
Also this error could be caused by other packages.
How to debug this further, since I have no Idea which package/ code-fragment is causing this.
The text was updated successfully, but these errors were encountered: