I noticed that I have been having issues deploying one of my gatsby sites lately.
The site builds without errors locally, but when I try to deploy to netlify, it fails with an error msg
“error UNHANDLED EXCEPTION write EPIPE”
The only thing I did was to update gatsby and its dependencies from 4.8 to 4.8.1. Everything was fine prior to this update. I’m not sure what triggered the error in ver 4.8.1 that ver 4.8 didn’t have? Is it the memory usage?
Chances are this is because of a memory increase in your build. Netlify limits you to 3GB, and Gatsby v4 seems to hit it. I’ve been able to try and work around this by removing chunks of static content on my site, but it looks like I’m going to be forced to move off as it’s been stated by Netlify this limit cannot increase.
Yeah I thought about the possibility this might be a memory-related issue, but what I don’t understand is that everything was building fine before I updated Gatsby deps from v 4.8 to v 4.8.1 and there’s no new content added to the site either. It would be great if there’s a way to check the memory usage in the log.
I’m having same problem today (3/12/2022).
Gatsby CLI 4.9.1, Gatsby 4.9.3.
Just upgraded from v3 (which I built and deployed earlier today).
V3 and V4 build fine on my machine.
I DO NOT have any Netlify packages explicitly in my package.json, but that was never a problem before.
I’m about to try adding GATSBY_CONCURRENT_DOWNLOAD to 16 in the Netlify env vars.
guys, a few days ago I updated from gatsby from gatsby 4.7.2 to 4.9.1 without any issue, only sometimes I had the EPIPE error but after redeploying it was resolved, but today almost every deploy fails! So I tried almost everything:
adding GATSBY_CONCURRENT_DOWNLOAD variable to 16
GATSBY_CPU_COUNT to 1
Rolled back to 4.7.2
Any ideas? something bad is going on today with netlify?
Thanks for reaching out! Sorry to hear you are experiencing difficulties.
When you say you have tried optimizing images, can you elaborate on that? My first thoughts here would be checking your source images to see if you can reduce their size. Have you addressed the size of source images yet?