Render switch instance after build

I am getting maximum allocation heap memory reached error.
The error goes away if i build it on the 25$ tier.

switching back to 7$ says it wont apply unless the triggered deploy succeeds.

is there any way around this? I just need 1 - 1.5 gb of ram for build.

if not i am switching to another paid serivce for less than 25$ a month with far better support than email that responds every 24h

Hi Darren,

Some node applications do not use all the memory that is available to them. You can look into setting max-old-space-size to an appropriate value for your applications needs and the instance type you are on.

Our builds machines actually have an 8gb limit for memory, regardless of the instance type, so you shouldn’t need to switch to a different instance type if your app just requires 1 - 1.5 GB of ram during the build.

I hope this helps - let me know if you have any further questions!


it fails
Exited with status 134 while running your code.

i have build command
export NODE_OPTIONS="--max-old-space-size=8192"; npm install; npm run build

it makes no sense how the 25$ plan works but 7$ plan doesn’t can somebody help please

hello, is there any solution?
if not i will be moving back to GCP.
would love a timeline or possibly an verbal acknowledgment

Hi Darren,

Taking a look at the failed deploys, it looks like you are hitting the maximum allocation heap memory on the service startup, which is not during the build phase, but after it. This will be subject to the instance type limits specified here.

I also looked at some of the historical metrics for your service, and do see that it has bumped into the memory limits for Starter in the past.

At the moment, we do not have the option to select higher limits for the service startup vs. when it’s running after, so you would need to select the instance type appropriate for your app’s resource usage on startup as well.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.