That could be true - but if it were, we’d have seen a lot more complaints than you and fvieira. But, here’s also a change log of what’s changing: Releases · netlify/build · GitHub.
For Gatsby 4, I think I’ve mentioned the cause - it’s most likely PQR. Gatsby says that it takes a lot more memory, so as long as you can set the CPU Count to 1, it should work. I don’t know why it’s causing issues on Gatsby 2 though. From my point of view, I think Gatsby is the one at fault here for consuming 6 GB and 8 GB memory. In all of the site builds that have failed due to lack of memory (at least on Netlify), Gatsby has accounted for the highest number. I have heard that Gatsby 4 has improved this by a huge margin, but seeing the above post doesn’t look too promising - however, it would be wrong to judge from one or two sites failing to build.
To be honest, I would not think this to be a Sanity API issue - because the task of an API is to return data - not much to do with memory consumption on the client-side. It’s understandable that you all think this is a Netlify issue - but a lot of Gatsby sites are currently also building correctly on Netlify - so not really sure who needs to own the blame here. So @fvieira, you can save yourself some trouble and not do a lot of testing - unless you’re extremely determined to.
@slashdata, you’re free to use AWS for your needs - you need not mention that in every other message. If Netlify is not suiting your use case, or if AWS is more suitable, we don’t wish to force you to use our platform - you’re free to make a switch. We won’t be happy about it, but we’d at least know where we need to improve.
Lastly, the warning that you’re seeing is not August 18 but November 15. It’s simply updating the build image and nothing is changing for you unless you manually upgrade. If you don’t upgrade, you won’t be able to build your sites after that date anymore, but that has nothing to do with this error.
I’m sorry, I do not have a better news for you both, but build failures due to running out of memory is not something we can possibly debug effectively. We’ve made the tools available (like the Netlify Build Image mentioned above), that you can use locally and see if there’s a specific limit at which your site builds fine, so you can try and optimise your process accordingly - and it has helped a few people in the past. They found some memory leaks and more optimal solutions to their codebases, which has helped them lower the memory consumption.
As I’ve said above, the upgraded limits of RAM in the build pods has been a fairly recent change - so until a few weeks ago, based on your descriptions, it sounds like you could have never been able to build sites on Netlify - at least not with Gatsby.
