We’ve had this compile-time error for the past few days and when we run the manual process, sometimes we get the following error.
But if we change the maximum memory from the NODE options, we get the first error in all builds.
Hi there, glad you found us!
First, have you looked through this resource? It is a compilation of all of our build and deploy resources. This is a good starting point.
If you have worked through those guides and are still encountering issues please share the following information:
- what you have already tried
- any error messages you have received in your terminal window or in the developer console
I also recommend you search the forums as this is a common error code and there are several solutions .
Hi @SamO ,
Yes, searched the forums and tried to apply one of the solutions, which was to increase memory, but this solution was worse.
I don’t know what else to do because the Netlify console doesn’t give me much information.
I don’t know if you can dig deeper and get more information from your side
Have you tried optimising your build process?
We couldn’t optimize our construction.
We currently use nuxt and for in express functions.
Right now it’s failing us more often than when I created this post.
What other option do we have to check this problem, is it possible to check from the administration because it sometimes fails ?
The error in your first screenshot shows “killed” as the error message, which means your build tried to use more than the 11 GB allocated RAM. This cannot be changed.
Hi Hrishikesh Kokate, when I change the “max-old-space-size” to 4096 does not solve the problem.
With that change or without the change I keep getting error codes 134 or 137.
What I find very strange is that the problem is not constant, sometimes the build is successfully finished by just giving it a retry. I would like to ask you if the agents are shared, that is, in the same agent you can run different compilations.
Secondly, I can disable the installation of Python, Go, and Ruby. We only use NodeJS.
Here are some recent links with the different errors.
Hi @hrishikesh, I am running the compilation on a docker with limited memory of 8GB and 4 CPU. In no time does the Netlify build command fail.
What I see is that at some point the Nuxt construction consumes 90% of the memory, but does not break the construction.
What could cause the current problem in Netlify?
Good morning @hrishikesh @SamO
I appreciate your collaboration with the problem described above, now it is almost impossible to perform a deployment.
We have seen that during the night or very early in the morning, they fail less often.
I’m not sure what more to suggest, @dcadenaallan. Even in the links you shared:
This again failed with the Heap issue that I mentioned earlier. Not sure if increasing the heap size further would work or not, but that’s the only solution for it.
Regarding the second link:
As mentioned before, it exceed the RAM limits:
So it crashed. This doesn’t have any solution apart from you having to optimise your build process, or build locally and deploying via CLI.
Regarding the OK build:
It was almost close to crashing as well. It does look like your build process is going out of platform limitations.
The only suggestion or workaround you can use right now is to build locally and deploy via CLI, or move that process to GitHub Actions or something so you can deploy from there.
Do you have any official Netlify Github Accion?
There is Netlify Action which is NOT affiliated with Netlify. Or are you referring to our Netlify Github account.
We are having problems with the deployment of branches from the CLI, unlike the deploy-previews and the production ones that are completed correctly.
A clear example would be with the master branch, deployment is made from GitHub actions with the CLI and no changes are seen.
yarn netlify:deploy --build "yarn netlify:build" --context "branch-deploy" --dir "dist" --functions ".netlify/functions" --json --message "Deploy from Github Actions" --debug --prod "false" --alias "master"
It is a known problem? that we could do?
Netlify CLI is not really meant to do branch deploys - and they don’t even work as real branch deploys. Sure, you can set an
alias, but that’s about it.
I believe your issue is happening due to specifying the
alias flag. I haven’t checked in detail for your site, but if you used to have a branch deploy with the same name that you’re trying to set as an alias, it would cause content not updating issue.