SEGFAULT on Node Fermium #34126
Comments
This comment has been minimized.
This comment has been minimized.
addaleax
added
buffer
|
Thanks for the report! I’ve reproduced this. It’s happening because the However, the good news is that #33291 fixes this, and is scheduled to be released today, as part of #34093. So all that we really need to do here is write a regression test. (The other good news is that this would typically only happen on process exit, so while the error is annoying, it doesn’t affect the functionality of the program.) |
3 tasks
addaleax
added a commit
to addaleax/node
that referenced
this issue
Jun 30, 2020
Add a test for a regression that occurs when transferring some `Buffer` objects that were created from C++ to a parent thread. Fixes: nodejs#34126
MylesBorins
pushed a commit
that referenced
this issue
Jul 14, 2020
Add a test for a regression that occurs when transferring some `Buffer` objects that were created from C++ to a parent thread. Fixes: #34126 PR-URL: #34140 Reviewed-By: Gerhard Stöbich <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Jul 16, 2020
Add a test for a regression that occurs when transferring some `Buffer` objects that were created from C++ to a parent thread. Fixes: #34126 PR-URL: #34140 Reviewed-By: Gerhard Stöbich <[email protected]>
addaleax
added a commit
that referenced
this issue
Sep 22, 2020
Add a test for a regression that occurs when transferring some `Buffer` objects that were created from C++ to a parent thread. Fixes: #34126 PR-URL: #34140 Reviewed-By: Gerhard Stöbich <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: v14.1.0 for me
Platform: Linux salathiel 5.4.0-39-generic The binary and long term compatibility with node #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Subsystem: (Ubuntu for me)
What steps will reproduce the bug?
I tried to build https://github.com/ever-co/gauzy -
yarn nx build api --configuration=productionand it landed me here nrwl/nx#2956 where other developers noticed that downgrading Node fixed the issue.How often does it reproduce? Is there a required condition?
To the exception of Node version, I have not noticed any other condition.
What is the expected behavior?
A successful build.
What do you see instead?
In Docker build
On host, it is silent and the exit status -
echo $?- returned is139, which happens to be NodeJS exit status for SEGFAULT.Additional information
It works after I downgraded to
node:erbium-alpine. Since the issue is not happening during development, I have not [yet] downgraded my environment.The text was updated successfully, but these errors were encountered: