Repository navigation
--max_old_space_size unreliable for values >= 2^31 #18786
Description
Activity
Can you post your question to the help repo? Thanks.
Reopening, see nodejs/help#1111 (comment). Looks like V8 is still using a 32 bits int to store
--max_old_space_size.- changed the title
[-]NOT Increasing Node (v4.5) process memory by using --max_old_space_size V8 option[/-][+]--max_old_space_size unreliable for values >= 2^31[/+]on Feb 20, 2018 Thanks a lot to take this further!
Is there any quick solution to overcome process out of memory issue other than code optimisation?
I tried --max_old_space_size=3072 (±3GB) but still FAILED!! :( in AWS production machine (but worked fine with local Mac osx machines)
Any workaround would be appreciated!
Thanks!
It would be great if you can suggest the maximum possible value for --max_old_space_size
Node JS version: 4.8.7Thanks!
I think you should be good with values < 2048.
- added a commit that references this issue
on Feb 21, 2018 Unfortunately still it is not working!
We're using PM2 to launch the Node instance and monitor. Here is the commandpm2 start /home/sever/src/bin/app.js -i 1 --name app_server --node-args="--max_old_space_size=2048"
- added a commit that references this issue
on Feb 22, 2018 - added 2 commits that reference this issue
on Mar 7, 2018 - added 2 commits that reference this issue
on May 8, 2018
Hello,
Unexpectedly terminating Node process due to out of memory issue and tried to extend memory size by setting Node - V8 option "--max_old_space_size". It works as expected in some machines but NOT consistent across machines and different applications (NOT working in pre-prod which is in AWS). Sometimes it decreasing memory too.
Doest it depending on any other factors? Kindly advice.
Node version - 4.5
Thanks!