Segmentation fault (core dumped) #5961
Comments
|
Ubuntu 20.04.1 LTS Doesn't happen with |
|
I am also seeing the error "Segmentation fault" with node |
|
What OS are you on? Can you run try running |
|
OS: macOS Big Sur 11.2.3 My issue is intermittent. It occurs maybe 1/10 of clean builds |
|
The issue also occurs on vercel which is running node 14.x (issue also occurred with node 12.x) |
|
The issue Sorry for the heads up, I bumped my node version and thought it worked |
|
I got similar issue on NixOS with Node.js 14.16.0 and 16.2.0. Works fine with My gdb session |
|
Same with Ubuntu 16.04 & Nodejs 14.15.4 & npm 6.14.10 & Parcel 2.0.0-beta.3.1. |
|
I cannot find any documentation about |
|
It exists in Parcel 1 and 2. parcel/packages/core/workers/src/WorkerFarm.js Lines 569 to 571 in ff6b7b4 |
|
Same issue here when building on Vercel |
|
I have not seen this issue again after I set |
|
Segmentation Fault happened here when i added image resizing:
|
|
Is everyone who's experiencing this crash also using the image resize/reformat feature? Do the crashes stop if you don't use that? |
|
Looks that way. I have no crashes after removing all image resizing code. |
|
We upgraded |
|
Yes, I've just upgraded to latest nightly and the problem seems to be gone. Thank you! |
|
Hey there, the issue might not be completely solved: There is however no mention to a segfault in the logs |
|
Are you sure it's a segfault? I would say the various |
|
I can't be sure, but |
|
Getting this issue "^2.0.0-rc.0" Running on alpine linux. |
|
I'm getting the segfault as well on Cloudflare Pages (but not locally). Parcel The workaround helps! |
|
I'm getting it on Netlify but not locally. Removing all image resizing fixes it. I tried with Sharp 0.29.0 also with same results. Netlify says it is because the VM/environment/Ubuntu/whatever runs out of memory. Running locally I'm only using about 800MB. Netflify claims they run the builds with 3GB. So...??? Anyway, I'll be investigating replacing Sharp with something else. |
|
I am getting this on Netlify and Cloudflare Pages on |
|
I also get this error when running build on Github Actions. I tried with |
|
I was also running into this issue on netlify with |
|
I think the issue is that sharp doesn't play well with Node's worker_threads, but I have been unable to reproduce the issue locally (only happens in Vercel for me). See https://sharp.pixelplumbing.com/install#worker-threads and lovell/sharp#2263. We're going to attempt to require sharp on the main thread before using it in a worker and see if that helps... #7001 |
|
Btw, another workaround is to use |
|
The fix in #7001 appears to work on Vercel without any workaround. 🥳 It's available in the latest nightly release. Hope it works for other setups as well. |
|
Seems to work on Netlify without workaround too now, thanks |
|
We (still) hit segfaults with both yarn and npm using parcel.js Luckily |
|
@felixbr what operating system are you using? Does it happen after a build completes, on exit, or at some other point? I'm debugging an issue with older glibc versions on CentOS that is related to this. |
|
It was on a Jenkins node running |
|
Ok thanks, that's where I'm seeing it as well... Still haven't gotten to the bottom of what's causing it. |
|
I've reduced this to a bug in Rust, combined with a bug in glibc. It is fixed in newer versions, but it is impossible to upgrade on CentOS 7 without upgrading the whole OS. I'm hoping the bug in Rust can be fixed to support older glibc versions. In the meantime, I am trying to find a workaround. See rust-lang/rust#91979. |
|
Hi, I just upgraded to v2.3.1. I'm getting this issue even with the workarounds. I'm running it on Mac OS 12.2.1. |
|
Here the same with parcel |
|
parcel 2.6.2 Node v16.16.0 Centos7 has the same problem. |
|
@harlanc , what I found out is that RHEL 7 is too old for these new Node versions. Under RHEL 8 it does not crash. Maybe you just need to upgrade your CentOS system too. |
Seems like we see a bunch of segfaults in parcel: parcel-bundler/parcel#5961
I have a consistant segfault on cold builds, it's reproducible:
https://github.com/GauBen/gauben.github.io/runs/2025608512
When the cache folder exists, there is no such problem:
https://github.com/GauBen/gauben.github.io/runs/2025668435
How to reproduce
Versions: node v15.11.0, yarn v1.22.5, parcel v2.0.0-nightly.612
Current workaround
(Only the first one segfaults)
Package.json: https://github.com/GauBen/gauben.github.io/blob/source/package.json
Originally posted by @GauBen in #5773 (comment)
The text was updated successfully, but these errors were encountered: