Experienced getting fatal build errors on our build server during ESLint linting of our React project:
<--- Last few GCs --->
[10012:0000000001DA2080] 184320 ms: Mark-sweep 2035.1 (2051.8) -> 2034.3 (2051.8) MB, 2297.9 / 0.0 ms (average mu = 0.114, current mu = 0.001) allocation failure scavenge might not succeed
[10012:0000000001DA2080] 185393 ms: Mark-sweep 2035.3 (2051.8) -> 2033.6 (2051.8) MB, 1068.8 / 0.0 ms (average mu = 0.077, current mu = 0.003) allocation failure scavenge might not succeed
The MB values looked very suspicious in that they were on either side of 2048 MB (2 GB), so suspected our project had run into some sort of limit. And seems there is indeed a max limit of ~2 GB by default on the heap size.
To increase the node heap size limit, set the
--max-old-space-size to something more than 2048, e.g. like this on Windows:
To verify that it actually works (or check what it is by default), this command seems to do it:
Note that the output for some reason always seem to be a bit more than what’s set as the limit. Not sure what that’s about, but anyways… ???????