CODEWITHSUNDEEP
javascriptnode.jscrashout-of-memoryheap-memory
Lapsio
Lapsio

Reputation: 7064

Node.js heap out of memory

Today I ran my script for filesystem indexing to refresh RAID files index and after 4h it crashed with following error:

[md5:]  241613/241627 97.5%  
[md5:]  241614/241627 97.5%  
[md5:]  241625/241627 98.1%
Creating missing list... (79570 files missing)
Creating new files list... (241627 new files)

<--- Last few GCs --->

11629672 ms: Mark-sweep 1174.6 (1426.5) -> 1172.4 (1418.3) MB, 659.9 / 0 ms [allocation failure] [GC in old space requested].
11630371 ms: Mark-sweep 1172.4 (1418.3) -> 1172.4 (1411.3) MB, 698.9 / 0 ms [allocation failure] [GC in old space requested].
11631105 ms: Mark-sweep 1172.4 (1411.3) -> 1172.4 (1389.3) MB, 733.5 / 0 ms [last resort gc].
11631778 ms: Mark-sweep 1172.4 (1389.3) -> 1172.4 (1368.3) MB, 673.6 / 0 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x3d1d329c9e59 <JS Object>
1: SparseJoinWithSeparatorJS(aka SparseJoinWithSeparatorJS) [native array.js:~84] [pc=0x3629ef689ad0] (this=0x3d1d32904189 <undefined>,w=0x2b690ce91071 <JS Array[241627]>,L=241627,M=0x3d1d329b4a11 <JS Function ConvertToString (SharedFunctionInfo 0x3d1d3294ef79)>,N=0x7c953bf4d49 <String[4]\: ,\n  >)
2: Join(aka Join) [native array.js:143] [pc=0x3629ef616696] (this=0x3d1d32904189 <undefin...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/usr/bin/node]
 2: 0xe2c5fc [/usr/bin/node]
 3: v8::Utils::ReportApiFailure(char const*, char const*) [/usr/bin/node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/bin/node]
 5: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/usr/bin/node]
 6: v8::internal::Runtime_SparseJoinWithSeparator(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/bin/node]
 7: 0x3629ef50961b

Server is equipped with 16gb RAM and 24gb SSD swap. I highly doubt my script exceeded 36gb of memory. At least it shouldn't

Script creates index of files stored as Array of Objects with files metadata (modification dates, permissions, etc, no big data)

Here's full script code: http://pastebin.com/mjaD76c3

I've already experiend weird node issues in the past with this script what forced me eg. split index into multiple files as node was glitching when working on such big files as String. Is there any way to improve nodejs memory management with huge datasets?

Upvotes: 596

Views: 1150181

Answers (30)

Maksim Luzik
Maksim Luzik

Reputation: 6703

If you want to increase the memory usage of the node globally - not only single script, you can export environment variable, like this:

export NODE_OPTIONS=--max_old_space_size=4096

Then you do not need to play with files when running builds like npm run build.

Upvotes: 293

Narges
Narges

Reputation: 49

October 2024, This line fixed it:

export NODE_OPTIONS="--max-old-space-size=6144"

Just add this line to terminal, and if you got the same error replace 6144 with one of these options:

#increase to 7gb => 7168

#increase to 8gb => 8192

Upvotes: 1

CenterADiv
CenterADiv

Reputation: 71

The Solution with the max-old-space-size also worked for me. Another suggestion: If you want to set the NODE OPTIONS per project you can simply use the .npmrc file. E.g in my project i configured this option so that each package.jsonscript will run with these options

.npmrc

node-options=--max-old-space-size=8192

The same as:

export NODE_OPTIONS="--max-old-space-size=8192" && npm run start

More details to global node options with .npmrc:

NPM Docs: https://docs.npmjs.com/cli/v9/using-npm/config#node-options

How to set NODE_OPTIONS for all package.json scripts at once?

Upvotes: 1

andi
andi

Reputation: 43

I also ran into this node-out-of-memory error.

Using NUXT3, I accidentally moved the node_modules directory into the pages directory.

So, NUXT tried to do its magic on each module file and node ran at some point into the limit.

Maybe my story is helpful to someone at some point :)

Upvotes: 0

Himanshu Shukla
Himanshu Shukla

Reputation: 51

A workaround I used when encountering a heap out of memory error in React was to modify the "start" property in the react-scripts object within the package.json file to:

  "start": "node --max-old-space-size=4096 ./node_modules/react-scripts/scripts/start.js"

Upvotes: 0

Bat-Orshikh Baavgaikhuu
Bat-Orshikh Baavgaikhuu

Reputation: 943

I just faced same problem with my EC2 instance t2.micro which has 1 GB memory.

I resolved the problem by creating swap file using this url and set following environment variable.

export NODE_OPTIONS=--max_old_space_size=4096

Finally the problem has gone.

Upvotes: 81

Gampesh
Gampesh

Reputation: 4374

In my case I had ran npm install on previous version of node, after some day I upgraded node version and ram npm install for few modules. After this I was getting this error. To fix this problem I deleted node_module folder from each project and ran npm install again.

Note : This was happening on my local machine and it got fixed on local machine only.

Upvotes: -1

Adrien Joly
Adrien Joly

Reputation: 5336

While using nodejs apps that produce heavy logging, a colleague solved this issue by piping the standard output(s) to a file.

Upvotes: 1

Pierrick Martelli&#232;re
Pierrick Martelli&#232;re

Reputation: 1665

My program was using two arrays. One that was parsed on JSON, the other that was generated from datas on the first one. Just before the second loop, I just had to set my first JSON parsed array back to [].

That way a lot of memory is freed, allowing the program to continue execution without failing memory allocation at some point.

Upvotes: 1

rgantla
rgantla

Reputation: 1956

For angular project bundling, I've added the below line to my pakage.json file in the scripts section.

"build-prod": "node --max_old_space_size=5120 ./node_modules/@angular/cli/bin/ng build --prod --base-href /"

Now, to bundle my code, I use npm run build-prod instead of ng build --requiredFlagsHere

Upvotes: 0

Akhilesh B Chandran
Akhilesh B Chandran

Reputation: 6608

I experienced the same problem today. The problem for me was, I was trying to import lot of data to the database in my NextJS project.

So what I did is, I installed win-node-env package like this:

yarn add win-node-env

Because my development machine was Windows. I installed it locally than globally. You can install it globally also like this: yarn global add win-node-env

And then in the package.json file of my NextJS project, I added another startup script like this:

"dev_more_mem": "NODE_OPTIONS=\"--max-old-space-size=8192\" next dev"

Here, am passing the node option, ie. setting 8GB as the limit. So my package.json file somewhat looks like this:

{
  "name": "my_project_name_here",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "dev_more_mem": "NODE_OPTIONS=\"--max-old-space-size=8192\" next dev",
    "build": "next build",
    "lint": "next lint"
  },
  ......
}

And then I run it like this:

yarn dev_more_mem

For me, I was facing the issue only on my development machine (because I was doing the importing of large data). Hence this solution. Thought to share this as it might come in handy for others.

Upvotes: 2

Sheikh Wahab Mahmood
Sheikh Wahab Mahmood

Reputation: 428

I have fixed in Angular by making some changes in package.json file:

"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build --prod --aot --build-optimizer",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
}

change your build to this it will solve the memory problem then run "npm run build" to build your project in production mode.

Upvotes: 0

Anupam Chaplot
Anupam Chaplot

Reputation: 1316

You can fix a "heap out of memory" error in Node.js by below approaches.

  1. Increase the amount of memory allocated to the Node.js process by using the --max-old-space-size flag when starting the application. For example, you can increase the limit to 4GB by running node --max-old-space-size=4096 index.js.

  2. Use a memory leak detection tool, such as the Node.js heap dump module, to identify and fix memory leaks in your application. You can also use the node inspector and use chrome://inspect to check memory usage.

  3. Optimize your code to reduce the amount of memory needed. This might involve reducing the size of data structures, reusing objects instead of creating new ones, or using more efficient algorithms.

  4. Use a garbage collector (GC) algorithm to manage memory automatically. Node.js uses the V8 engine's garbage collector by default, but you can also use other GC algorithms such as the Garbage Collection in Node.js

  5. Use a containerization technology like Docker which limits the amount of memory available to the container.

  6. Use a process manager like pm2 which allows to automatically restart the node application if it goes out of memory.

Upvotes: -2

Symeon Mattes
Symeon Mattes

Reputation: 1268

I had the same issue in a windows machine and I noticed that for some reason it didn't work in git bash, but it was working in power shell

Upvotes: 1

JSON C11
JSON C11

Reputation: 11792

--max-old-space-size

Unix (Mac OS)

  1. Open a terminal and open our .zshrc file using nano like so (this will create one, if one doesn't exist):

    nano ~/.zshrc

  2. Update our NODE_OPTIONS environment variable by adding the following line into our currently open .zshrc file:

    export NODE_OPTIONS=--max-old-space-size=8192 # increase node memory limit

Please note that we can set the number of megabytes passed in to whatever we like, provided our system has enough memory (here we are passing in 8192 megabytes which is roughly 8 GB).

  1. Save and exit nano by pressing: ctrl + x, then y to agree and finally enter to save the changes.

  2. Close and reopen the terminal to make sure our changes have been recognised.

  3. We can print out the contents of our .zshrc file to see if our changes were saved like so: cat ~/.zshrc.

Linux (Ubuntu)

  1. Open a terminal and open the .bashrc file using nano like so:

    nano ~/.bashrc

The remaining steps are similar with the Mac steps from above, except we would most likely be using ~/.bashrc by default (as opposed to ~/.zshrc). So these values would need to be substituted!

Link to Nodejs Docs

Upvotes: 8

atazmin
atazmin

Reputation: 5667

I had this error on AWS Elastic Beanstalk, upgrading instance type from t3.micro (Free tier) to t3.small fixed the error

Upvotes: 3

cansu
cansu

Reputation: 1144

I will mention 2 types of solution.

My solution : In my case I add this to my environment variables :

export NODE_OPTIONS=--max_old_space_size=20480

But even if I restart my computer it still does not work. My project folder is in d:\ disk. So I remove my project to c:\ disk and it worked.

My team mate's solution : package.json configuration is worked also.

"start": "rimraf ./build && react-scripts --expose-gc --max_old_space_size=4096 start",

Upvotes: 10

Ramone Graham
Ramone Graham

Reputation: 1

Check that you did not install the 32-bit version of node on a 64-bit machine. If you are running node on a 64-bit or 32-bit machine then the nodejs folder should be located in Program Files and Program Files (x86) respectively.

Upvotes: -2

Ashokan Sivapragasam
Ashokan Sivapragasam

Reputation: 2189

If you have limited memory or RAM, then go for the following command.

ng serve --source-map=false

It will be able to launch the application. For my example, it needs 16gb RAM. But I can run with 8gb RAM.

Upvotes: -1

Shoaib Iqbal
Shoaib Iqbal

Reputation: 2730

If any of the given answers are not working for you, check your installed node if it compatible (i.e 32bit or 64bit) to your system. Usually this type of error occurs because of incompatible node and OS versions and terminal/system will not tell you about that but will keep you giving out of memory error.

Upvotes: 1

The epic face 007
The epic face 007

Reputation: 629

Use the option --optimize-for-size. It's going to focus on using less ram.

Upvotes: 4

sidverma
sidverma

Reputation: 1185

Recently, in one of my project ran into same problem. Tried couple of things which anyone can try as a debugging to identify the root cause:

  1. As everyone suggested , increase the memory limit in node by adding this command:

    {
   "scripts":{
      "server":"node --max-old-space-size={size-value} server/index.js"
   }
}

Here size-value i have defined for my application was 1536 (as my kubernetes pod memory was 2 GB limit , request 1.5 GB)

So always define the size-value based on your frontend infrastructure/architecture limit (little lesser than limit)

One strict callout here in the above command, use --max-old-space-size after node command not after the filename server/index.js.

  1. If you have ngnix config file then check following things:

    • worker_connections: 16384 (for heavy frontend applications) [nginx default is 512 connections per worker, which is too low for modern applications]

    • use: epoll (efficient method) [nginx supports a variety of connection processing methods]

    • http: add following things to free your worker from getting busy in handling some unwanted task. (client_body_timeout , reset_timeout_connection , client_header_timeout,keepalive_timeout ,send_timeout).

  2. Remove all logging/tracking tools like APM , Kafka , UTM tracking, Prerender (SEO) etc middlewares or turn off.

  3. Now code level debugging: In your main server file , remove unwanted console.log which is just printing a message.

  4. Now check for every server route i.e app.get() , app.post() ... below scenarios:

  • data => if(data) res.send(data) // do you really need to wait for data or that api returns something in response which i have to wait for?? , If not then modify like this:
data => res.send(data) // this will not block your thread, apply everywhere where it's needed

  • else part: if there is no error coming then simply return res.send({}) , NO console.log here.

  • error part: some people define as error or err which creates confusion and mistakes. like this:

    `error => { next(err) } // here err is undefined`

 `err => {next(error) } // here error is undefined`

 `app.get(API , (re,res) =>{
     error => next(error) // here next is not defined
  })`

  • remove winston , elastic-epm-node other unused libraries using npx depcheck command.

  • In the axios service file , check the methods and logging properly or not like :

      if(successCB) console.log("success") successCB(response.data) // here it's wrong statement, because on success you are just logging and then `successCB` sending  outside the if block which return in failure case also.

  • Save yourself from using stringify , parse etc on accessive large dataset. (which i can see in your above shown logs too.

  1. Last but not least , for every time when your application crashes or pods restarted check the logs. In log specifically look for this section: Security context This will give you why , where and who is the culprit behind the crash.

Upvotes: 11

Arvind Chourasiya
Arvind Chourasiya

Reputation: 17372

For Angular, this is how I fixed

In Package.json, inside script tag add this

"scripts": {
  "build-prod": "node --max_old_space_size=5048 ./node_modules/@angular/cli/bin/ng build --prod",
},

Now in terminal/cmd instead of using ng build --prod just use

npm run build-prod

If you want to use this configuration for build only just remove --prod from all the 3 places

Upvotes: 2

FiringBlanks
FiringBlanks

Reputation: 2084

You can also change Window's environment variables with:

 $env:NODE_OPTIONS="--max-old-space-size=8192"

Upvotes: 6

Irina Sargu
Irina Sargu

Reputation: 81

For other beginners like me, who didn't find any suitable solution for this error, check the node version installed (x32, x64, x86). I have a 64-bit CPU and I've installed x86 node version, which caused the CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory error.

Upvotes: 8

Angela Rana
Angela Rana

Reputation: 29

In my case, I upgraded node.js version to latest (version 12.8.0) and it worked like a charm.

Upvotes: 2

Umang Patwa
Umang Patwa

Reputation: 2965

Steps to fix this issue (In Windows) -

  1. Open command prompt and type %appdata% press enter
  2. Navigate to %appdata% > npm folder
  3. Open or Edit ng.cmd in your favorite editor
  4. Add --max_old_space_size=8192 to the IF and ELSE block

Your node.cmd file looks like this after the change:

@IF EXIST "%~dp0\node.exe" (
  "%~dp0\node.exe" "--max_old_space_size=8192" "%~dp0\node_modules\@angular\cli\bin\ng" %*
) ELSE (
  @SETLOCAL
  @SET PATHEXT=%PATHEXT:;.JS;=;%
  node "--max_old_space_size=8192" "%~dp0\node_modules\@angular\cli\bin\ng" %*
)

Upvotes: 16

jbaylina
jbaylina

Reputation: 4698

I just want to add that in some systems, even increasing the node memory limit with --max-old-space-size, it's not enough and there is an OS error like this:

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)

In this case, probably is because you reached the max mmap per process.

You can check the max_map_count by running

sysctl vm.max_map_count

and increas it by running

sysctl -w vm.max_map_count=655300

and fix it to not be reset after a reboot by adding this line

vm.max_map_count=655300

in /etc/sysctl.conf file.

Check here for more info.

A good method to analyse the error is by run the process with strace

strace node --max-old-space-size=128000 my_memory_consuming_process.js

Upvotes: 31

Ahmed Aboud
Ahmed Aboud

Reputation: 1322

if you want to change the memory globally for node (windows) go to advanced system settings -> environment variables -> new user variable 

variable name = NODE_OPTIONS
variable value = --max-old-space-size=4096

Upvotes: 6

Venkat.R
Venkat.R

Reputation: 7736

I've faced this same problem recently and came across to this thread but my problem was with React App. Below changes in the node start command solved my issues.

Syntax

node --max-old-space-size=<size> path-to/fileName.js

Example

node --max-old-space-size=16000 scripts/build.js

Why size is 16000 in max-old-space-size?

Basically, it varies depends on the allocated memory to that thread and your node settings.

How to verify and give right size?

This is basically stay in our engine v8. below code helps you to understand the Heap Size of your local node v8 engine.

const v8 = require('v8');
const totalHeapSize = v8.getHeapStatistics().total_available_size;
const totalHeapSizeGb = (totalHeapSize / 1024 / 1024 / 1024).toFixed(2);
console.log('totalHeapSizeGb: ', totalHeapSizeGb);

Upvotes: 21

Related Questions