FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory in Ionic 3

Question

When I run an Ionic 3 project using the ionic serve command, then I am getting this error:

check this answer: https://stackoverflow.com/questions/38558989/node-js-heap-out-of-memory/66914674#66914674 — sidverma, Apr 02 '21 at 06:42

score 629 · Answer 1 · edited Jul 13 '23 at 15:35

629

For a non-Angular general answer for those who land on this question from Google:

Most times when you face this error it’s probably because of a memory leak, an addition/version upgrade of a library or a difference in how Node.js manages memory between versions (e.g. Node.js version <= 10 and Node.js version > 10).

Usually just increasing the memory allocated to Node.js will allow your program to run but may not actually solve the real problem and the memory used by the node process could still exceed the new memory you allocate. I'd advise profiling memory usage in your Node.js process when it starts running or updating to Node.js > 10.

I had a memory leak. Here is a great article on debugging memory leaks in Node.js.

That said, to increase the memory, in the terminal where you run your Node.js process:

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

Or for Windows:

Set NODE_OPTIONS="--max-old-space-size=8192"

where values of max-old-space-size can be: [2048, 4096, 8192, 16384] etc

More examples for further clarity:

export NODE_OPTIONS="--max-old-space-size=5120" # Increase to 5 GB
export NODE_OPTIONS="--max-old-space-size=6144" # Increase to 6 GB
export NODE_OPTIONS="--max-old-space-size=7168" # Increase to 7 GB
export NODE_OPTIONS="--max-old-space-size=8192" # Increase to 8 GB

# and so on...

# formula:
export NODE_OPTIONS="--max-old-space-size=(X * 1024)" # Increase to X GB

# Note: it doesn't have to be multiples of 1024.
# max-old-space-size can be any number of memory megabytes (MB) you have available.

See the current value of max-old-space-size (in MB)

To see the current (not exact but very close) value of max-old-space-size (in MB), run in your terminal

node -e 'console.log(v8.getHeapStatistics().heap_size_limit/(1024*1024))'

edited Jul 13 '23 at 15:35

Bakr

117
8

answered Jan 03 '20 at 03:49

Emmanuel N K

8,710
1
31
37

62

FYI, the default is 512 MB. You don't need to jump straight to 10x that amount, you could try something between 512 and 5120 first. – Cameron Hudson Jun 22 '20 at 22:42
2

Thanks this works for all types of application having memory issues. – invinciblemuffi Aug 12 '20 at 07:10
42

Just want to point out - thats its not always indicative of a memory leak. Perhaps a library you are using is using a bit more memory than it used to. For us `next.js` began crashing our app with the fast refresh feature. – Daniel Cooke Oct 20 '20 at 12:09
1

@DanielCooke what value you used for next js? can you please share what solution you used for this issue with next js – MSD Dec 04 '20 at 20:58
@MSD We seem to get by with 4096 max-old-space-size with next > 9.6. For production builds and dev – Daniel Cooke Dec 09 '20 at 14:11
@DanielCooke thanks ... tried that not working for me – MSD Dec 11 '20 at 12:11
2

Here are the docs https://nodejs.org/api/cli.html#cli_max_old_space_size_size_in_megabytes and nothing suggests that there should be steps of `integer * 1024`. – Mikhail Vasin Jul 21 '21 at 13:40
3

@MikhailVasin See the very last comments in my answer. I know it doesn't. I just put that there for those that want the common memory increments in GB. – Emmanuel N K Jul 21 '21 at 18:30
Is it just window thing? In windows, I had to use "max_old_space_size" instead of "max-old-space-size" (so use an underscore instead of a dash). – newman Feb 05 '22 at 16:08
During export 2.5 Lakh record in Excel Sheet. I have faced same issue. After run below command export NODE_OPTIONS="--max-old-space-size=5120" my issue is Resolved. – Dhaval Mojidra Oct 19 '22 at 09:36

score 103 · Answer 2 · edited Sep 30 '21 at 12:11

103

In my case, I fixed this problem by installing Node.js, version 12.10.0.

edited Sep 30 '21 at 12:11

Peter Mortensen

30,738
21
105
131

answered Sep 17 '19 at 20:00

Germán Ayala

1,175
1
7
3

1

Same here. I've just changed the version and its works. – brunocascio Nov 20 '19 at 18:40
26

For context, Node 12 has a different heap management strategy which is based on available memory instead of using defaults. More details here: https://foundation.nodejs.org/announcements/2019/04/24/node-js-foundation-and-js-foundation-merge-to-form-openjs-foundation-2 – Derek Dowling Dec 19 '19 at 01:20
Nothing else worked for me, this was it. Thank you so much :) – Hussain Alaidarous Jan 07 '20 at 12:54
We updated to Node 12 and the error went away, easier than managing heap on Node 10 – Raffaeu May 25 '20 at 09:12
This fixed the issue. It should be accepted as the answer – Nitish Kumar May 27 '20 at 18:33
1

@NitishKumar I'm still receiving the error with Node 12 /shrug. The accepted should be whichever best solves the OP's use case -- though you'd've hoped they would have selected one of the answers at this point. – ruffin Jun 22 '20 at 20:35
this one only worked for me but in angular project. – Anup Bangale Jun 30 '20 at 11:40
2

@DerekDowling Wayback cause link broken: https://web.archive.org/web/20191103115941/https://foundation.nodejs.org/announcements/2019/04/24/node-js-foundation-and-js-foundation-merge-to-form-openjs-foundation-2 – Grim Aug 27 '20 at 08:15
I am using node 12.18.3 and got this error. – RyanNerd May 12 '21 at 10:09
I was using node 11.15.0, while making build got "Allocation failed - JavaScript heap out of memory", After updating to node 12.10.0(nvm install 12.10.0) everything works like a charm!!! – Alphonse R. Dsouza Nov 24 '21 at 10:03

score 87 · Answer 3 · edited Sep 30 '21 at 11:54

87

Just type this in the terminal:

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

The error occurs when you exceed the default maximum memory allowed for Node.js. All this does is increase the maximum memory allowed.

edited Sep 30 '21 at 11:54

Peter Mortensen

30,738
21
105
131

answered Nov 05 '20 at 23:34

Matt

33,328
25
83
97

3

This is the solution if you are working on the shell – Kareem Khaleel Sep 02 '21 at 10:43
@Matt can you add to your solution, how to see the existing value for "--max-old-space-size" before we actually tweak it? – klewis Nov 18 '22 at 17:57

score 85 · Answer 4 · edited Sep 30 '21 at 12:08

85

I had the same issue on CentOS server 7, but this solved my problem:

node --max-old-space-size=X node_modules/@angular/cli/bin/ng build --prod

Where X = (2048 or 4096 or 8192 o..) is the value of memory.

edited Sep 30 '21 at 12:08

Peter Mortensen

30,738
21
105
131

answered Apr 06 '19 at 09:55

Hakim CHRIFI ALAOUI

857
1
7
4

3

after changing the value of x.. error remains the same – Sohail Ahmad Sep 13 '19 at 14:05
1

If the error continues, keep increasing the size until there is enough memory to process which will eventually prevent the error. The only time I found I couldn't get past this error was with `ng serve` and a _massive_ .js file referenced in the `scripts` section of `angular.json` that needed to be loaded into memory. – atconway Nov 05 '19 at 22:04
can I set the value of X greater than 8192? I have 32GB of RAM – Diego Dec 27 '19 at 16:36
for me, supplying max-old-space-size on the command line did NOT work. This MAY be an interaction with nvm based node? instead inside a bash script, i used 'NODE_OPTIONS="--max-old-space-size=2048" node $NG build --prod --progress=false' which worked, as opposed to 'node --max-old-space-size=2048 $NG build --prod --progress=false' which did not. I still don not know why. – Simon H Jul 23 '20 at 10:38
if you run this inside docker and get KILLED error, increase the RAM allocated to docker engine as well. – Nima Ajdari Mar 17 '21 at 09:59

score 62 · Answer 5 · edited Oct 24 '21 at 22:52

62

I got the same error when I execute ng build command in Visual Studio Code. But I can build successfully when I execute the same thing on the Windows command line in the following sequence.

Step 1.

set NODE_OPTIONS=--max_old_space_size=4096

Step 2.

ng build

edited Oct 24 '21 at 22:52

Peter Mortensen

30,738
21
105
131

answered Mar 02 '20 at 08:58

Sushrut Singh Sisodiya

942
6
11

Thanks that helped me a lot, just switched my terminal – Gayatri Dipali Jan 09 '21 at 10:02
I have added it to file bath `/Users/MY_USER/.nvm/versions/node/v10.13.0/lib/node_modules/npm/bin/npm.cmd` it works fine – Ahmed Wahba Dec 05 '21 at 10:29
This work for me on GIT Bash. – Syed Uzair Uddin Jan 13 '22 at 12:24

score 41 · Answer 6 · edited Oct 24 '21 at 20:59

41

Try this solution which was pointed out in an old message on the forum: 3.7.0: iOS build with --prod not working

Open node_modules/@ionic/app-scripts/bin/ionic-app-scripts.js

Change the first line from:

#!/usr/bin/env node

to

#!/usr/bin/env node --max-old-space-size=4096

Try values 1024 and 2048, but for a relatively large app you may need 4096.

edited Oct 24 '21 at 20:59

Peter Mortensen

30,738
21
105
131

answered Nov 16 '18 at 18:12

runnerpaul

5,942
8
49
118

You should not change the scripts inside node_modules. – Faizi Mar 12 '21 at 11:52
This is a patch, temporary solution – Braian Mellor May 16 '23 at 14:21

score 39 · Answer 7 · edited Oct 24 '21 at 23:37

39

Windows

From the control panel go to System → Advanced system settings → Environment Variables → New (user or system)

Or this can be done in PowerShell with:

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

You can also increase this number, if necessary. We've seen folks need to increase this up to 14 GB for some larger projects!

Linux/macOS

export NODE_OPTIONS=--max-old-space-size=8192

edited Oct 24 '21 at 23:37

Peter Mortensen

30,738
21
105
131

answered Oct 02 '21 at 14:13

Mubarak Patel

416
4
3

I have nodeJS 10.15.3, i tried the NODE-OPTIONS solution on Windows 10 but it didn't work. Is there any other solutions ? – VenomBerry Oct 05 '21 at 10:07
@VenomBerry could you run WSL? Why hurt yourself by running this stuff on standard windows without a linux subsystem. – Evert Oct 18 '21 at 18:21
1

It looks like now we have to use `max-old-space-size=8192` without leading dashes in the System Settings. With `--` I got `Fatal javascript OOM in GC during deserialization` error in Node.js. But probably it is related to the latest versions only. – it3xl Dec 15 '21 at 17:12
1

@it3xl with newer node versions you still need to use -- or it won't be read as a change. The issue you are experiencing is that (at least some) newer versions of node node actually adds 24 bytes to the number you ask for, so asking for 4096MB turns into 4294967320 bytes, or 4096.00002MB which node can't deserialize... Try 4000 – mrVandal Jan 04 '22 at 13:05
How can we see what that value is before we tweak it?? – klewis Nov 18 '22 at 17:59
This worked for me. Needed to also restart Visual Studio Code. – Martin Staufcik Apr 25 '23 at 17:29

score 20 · Answer 8 · edited Oct 24 '21 at 22:54

20

In my case it was a recursion that was causing React to use up all memory.

This happened when I was refactoring my code and didn't notice this.

const SumComponent = () => {
  return (
    <>
      <SumComponent />
    </>
  )
}

In other Node.js applications this might look like:

const someFunction = () => {
  ...
  someFunction();
  ...
}

edited Oct 24 '21 at 22:54

Peter Mortensen

30,738
21
105
131

answered Mar 15 '20 at 23:01

Ikhlak S.

8,578
10
57
77

2

Why was this a problem? <>> should be valid in React instead of using right? – Joelgullander Mar 18 '20 at 13:44
@Codehiker Yep its a new syntax in React 16 – Ikhlak S. Mar 19 '20 at 20:13
9

The recursion is that `SumComponent` contains a `SumComponent` (which contains a `SumComponent` which contains a `SumComponent`... ) – stone Jun 09 '20 at 07:11

score 16 · Answer 9 · edited Oct 24 '21 at 21:00

16

I got the same error message when I executed the following statements in Visual Studio Code. But I can build successfully when I execute the same thing in on the Windows command line.

npm install -g increase-memory-limit
increase-memory-limit
set NODE_OPTIONS=--max_old_space_size=4096
ng build -c deploy --build-optimizer --aot --prod --sourceMap

edited Oct 24 '21 at 21:00

Peter Mortensen

30,738
21
105
131

answered Nov 19 '19 at 02:47

heinels

189
1
6

1

directly setting --max_old_space_size=4096 in npm script or as node_options wasnt working for me it started working after installing what you stated. THANK YOU!!!!! – Caner Mar 24 '22 at 15:01

Hakan Fıstık · Answer 10 · 2021-09-30T13:07:47.950

15

Updating from Node.js 12 to Node.js 14 solved the problem for me.

Update
Now Node.js 16 is available, and I recommend updating to the latest available version of Node.js.

edited Sep 30 '21 at 13:07

answered Nov 12 '20 at 12:39

Hakan Fıstık

16,800
14
110
131

Yep, using `16.4.2` with Angular 11 fixed it for me. – DoubleA Feb 16 '22 at 12:39

score 10 · Answer 11 · answered Jan 18 '22 at 11:29

export NODE_OPTIONS="--max-old-space-size=6144" #it will increase to 6gb.

-------If Not Solved try this 2nd step------------- 2) Just update your node version to the latest one will solve this issue.

-------If Not Solved try this 3rd step------------- 3)Just run this command in your windows terminal. set NODE_OPTIONS=--max_old_space_size=4096

score 9 · Answer 12 · edited Jun 16 '19 at 12:41

9

node --max_old_space_size=4096 node_modules/@angular/cli/bin/ng build --baseHref=/baseUrl/ --prod=true

edited Jun 16 '19 at 12:41

double-beep

5,031
17
33
41

answered Jun 16 '19 at 12:38

Mohammad lockman

158
1
6

32

While this code may answer the question, providing additional context regarding why and/or how this code answers the question improves its long-term value. – Eric Leschinski Jun 17 '19 at 01:07

score 9 · Answer 13 · edited Oct 24 '21 at 22:48

9

For some reasons all the previous answers didn't really work for me. I did the following to fix my issue:

I had to first delete the node_modules folder
reinstall Node.js on my PC and
then npm install

edited Oct 24 '21 at 22:48

Peter Mortensen

30,738
21
105
131

answered Jan 14 '20 at 11:37

Samuel Olubayo

135
1
8

step 2 is not mandatory. I tried upper solution and it worked for me without step 2 as well – Analyst Sep 22 '20 at 07:45
1

well you may not need step 2, i only shared what worked for me :) – Samuel Olubayo Nov 20 '20 at 23:43

score 9 · Answer 14 · edited Oct 24 '21 at 22:58

Adding parameter --build-optimizer resolved the issue in my case:

node --max_old_space_size=4096 ./node_modules/@angular/cli/bin/ng build --prod --build-optimizer

I am not sure why adding only --build-optimizer solves the issue, but as per the Angular documentation it should be used with ahead-of-time (AOT) compilation enabled, so the updated command should be like below:

--build-optimizer=true --aot=true

Angular build documentation

score 9 · Answer 15 · answered Nov 21 '20 at 17:58

9

For me, I had a syntax error (which didn't show up) and caused this error.

answered Nov 21 '20 at 17:58

JoshuaRDBrown

343
5
12

1

I had the same issue. Thanks! – Ajay Lingayat Mar 30 '21 at 19:59
In my case it is forgot to remove a comma at the end of ngClass. Hope it could help someone. – Terry Windwalker Oct 30 '21 at 08:54
Oh god, I have something like `import { async } from '../../../../public/js/app'` in my code for some reason. You just saved me some good hours! – Dale Ryan Aug 23 '22 at 09:48

Sarath Mohandas · Answer 16 · 2020-02-06T10:25:19.307

7

Replace the line

"start": "ng serve -o --port 4300 --configuration=en" with

"start": "node --max_old_space_size=5096 node_modules/@angular/cli/bin/ng serve -o --port 4300 --configuration=en"

NOTE:

port--4300 is not constant depends upon which port you selects.
--max_old_space_size=5096 too not constant; any value 1024,2048,4096 etc

edited Feb 06 '20 at 10:25

answered Feb 06 '20 at 07:11

Sarath Mohandas

472
1
9
25

1

This one worked for me. Setting the `NODE_OPTIONS` from the command line didn't work, I'm guessing because Visual Studio uses a new process or something. Hard coding the change into my package.json `scripts` block solved it. – user101289 Mar 30 '21 at 14:46

score 6 · Answer 17 · answered Oct 03 '19 at 10:18

6

Run this command in your project folder. Use serve instead of build

node --max_old_space_size=8000 node_modules/@angular/cli/bin/ng serve  --prod --port=4202

answered Oct 03 '19 at 10:18

Deepu Reghunath

8,132
2
38
47

score 6 · Answer 18 · edited Jun 08 '21 at 07:43

6

I faced the same problem on Angular. Then I wrote

"serve": "node --max_old_space_size=8192 ./node_modules/@angular/cli/bin/ng serve"

this script to package.json scripts and for me this problem solved.

And run project this command:

npm run serve

edited Jun 08 '21 at 07:43

Ramil Aliyev 007

4,437
2
31
47

answered Jun 08 '21 at 07:16

Ali Alizade

113
1
4

This is close to incomprehensible. Can you fix it? – Peter Mortensen Oct 24 '21 at 23:28
First of all you must add the script to the scripts block into the package.json after all you must run the project with this command: `npm run serve` - @PeterSmith – Ali Alizade Oct 26 '21 at 07:37

score 5 · Answer 19 · answered Mar 12 '21 at 16:33

Instead of using ng build, I have executed below command in terminal to fix this issue.

 node --max_old_space_size=8192 ./node_modules/@angular/cli/bin/ng build --prod

Then do ng serve.

This is how my terminal look like

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS D:\ProjectPath\Project1> node --max_old_space_size=8192 ./node_modules/@angular/cli/bin/ng build --prod

`--prod` is now deprecated, use `--configuration production` instead — DFSFOT, Jun 06 '21 at 19:22

score 5 · Answer 20 · answered Dec 05 '21 at 05:05

Run this command:

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

To check how much you have already:

> node
> v8.getHeapStatistics()
{
  total_heap_size: 6049792,
  total_heap_size_executable: 524288,
  total_physical_size: 5477720,
  total_available_size: 1094444024,
  used_heap_size: 4141728,
  heap_size_limit: 1098907648,
  malloced_memory: 8192,
  peak_malloced_memory: 582752,
  does_zap_garbage: 0,
  number_of_native_contexts: 2,
  number_of_detached_contexts: 0
}

and then heap_size_limit: 1098907648

score 4 · Answer 21 · edited Sep 30 '21 at 12:09

4

For me it was a problem with a Firebase package.

Only add "@firebase/database": "0.2.1" for your package.json file. Reinstall node_modules and it works.

edited Sep 30 '21 at 12:09

Peter Mortensen

30,738
21
105
131

answered Apr 15 '19 at 07:24

Pol Fernández

1,198
9
14

*[a](https://www.youtube.com/watch?v=1Dax90QyXgI&t=17m54s) Firebase package* or *the Firebase package*? – Peter Mortensen Sep 30 '21 at 12:10

score 3 · Answer 22 · edited Oct 24 '21 at 21:04

3

I deleted the existing Node.js module and ran the below commands to fix my issue:

npm install -all
npm audit fix

edited Oct 24 '21 at 21:04

Peter Mortensen

30,738
21
105
131

answered Dec 09 '19 at 13:59

Pritiranjan Swain

81
6

score 3 · Answer 23 · answered May 18 '20 at 21:05

3

For me, the issue was having an extra node_modules folder that I renamed to node_modules_old and running an npm install to generate a fresh node_modules. Somehow the build must have still been picking up the node_modules_old folder, so I moved node_modules_old out of the directory to fix the issue.

answered May 18 '20 at 21:05

badjr

2,166
3
20
31

1

This was my issue. Had a `node_modules.old` folder when testing a different set of packages earlier. – user995551 Sep 23 '22 at 22:29

score 2 · Answer 24 · edited Oct 24 '21 at 23:03

2

Please check your Node.js version:

   node -v

If it’s 10.1.1 something, then you need to update your root level Node.js version via the below commands:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash

source ~/.nvm/nvm.sh

nvm ls

nvm install 12.18.1

Once done, please restart your terminal or Visual Studio.

It's working 100$.

For Ionic users, please add the below code in your package.json

 "ionic:build": "node --max-old-space-size=16384 ./node_modules/@ionic/app-scripts/bin/ionic-app-scripts.js build",

edited Oct 24 '21 at 23:03

Peter Mortensen

30,738
21
105
131

answered Jun 25 '20 at 14:35

Yogesh Kumar

1,016
11
10

actually this works if your building web through `app-scripts`, but if you build android or script like `ionic cordova build android` how? – Muhammed Moussa Jul 20 '20 at 16:21

score 2 · Answer 25 · edited Oct 24 '21 at 23:16

Another non-Angular answer (I was facing the same issue building a React application on AWS Amplify).

As mentioned by Emmanuel, it seems that it comes from the difference in the way memory is handled by Node.js v10 vs. Node.js v12.

I tried to increase memory with no avail. But using Node.js v12 did it.

Check how you can add nvm use $VERSION_NODE_12 to your build settings as explained by richard

frontend:
  phases:
    preBuild:
      commands:
        - nvm use $VERSION_NODE_12
        - npm ci
    build:
      commands:
        - nvm use $VERSION_NODE_12
        - node -v
        - npm run-script build

score 2 · Answer 26 · edited Sep 30 '21 at 11:51

2

Just run this command:

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

edited Sep 30 '21 at 11:51

Peter Mortensen

30,738
21
105
131

answered Mar 08 '21 at 23:30

Manoj Alwis

1,337
11
24

score 2 · Answer 27 · answered Apr 02 '23 at 09:15

2

Happened to me after Upgrading react and react-native libraries.
Solved by:

rm -rf node_modules **/node_modules && rm -rf yarn.lock **/yarn.lock && yarn cache clean && yarn install

answered Apr 02 '23 at 09:15

chenop

4,743
4
41
65

For me running yarn cache clean did the trick. – PHZ.fi-Pharazon Jul 04 '23 at 10:07

score 1 · Answer 28 · answered Aug 19 '20 at 11:42

1

I guess there are plenty of ways to reach this error!

On my side, I had a loop in my package.json. Project A had a dependency on project B, that had a dependency on project A.

answered Aug 19 '20 at 11:42

Remi

51
6

score 1 · Answer 29 · edited Oct 24 '21 at 23:27

1

If you are developing on Windows and running into this issue while publishing, upgrade Node.js through the official site.

The memory usage handling does increase with each newer version of Node.js, although I did not find exact numbers on what the increase is.

That was the only solution that worked for me. It took a whole weekend and more for me to solve this issue.

edited Oct 24 '21 at 23:27

Peter Mortensen

30,738
21
105
131

answered Jun 02 '21 at 16:29

nixish

21
3

score 1 · Answer 30 · edited Oct 24 '21 at 23:33

1

I am using the latest stable version of Node.js v-14.17. I was having the same issue with new Angular Ionic projects and tried most of the previous answers without success.

Finally after upgrading to Node.js 16.4.2 LTS, it fixed this issue.

edited Oct 24 '21 at 23:33

Peter Mortensen

30,738
21
105
131

answered Aug 13 '21 at 21:25

Vishal Kumar

4,419
1
25
31

Azure devops - After upgrading the task of node.js version from 10 to 12, it has resolved the pipeline error. – Karan Jun 28 '22 at 07:25

score 0 · Answer 31 · edited Oct 24 '21 at 21:02

0

Check your folder name. If your folder name has spaces, these kind of issues will be generated. Rename without spaces.

edited Oct 24 '21 at 21:02

Peter Mortensen

30,738
21
105
131

answered Nov 28 '19 at 10:12

Roney Francis

356
2
15

score 0 · Answer 32 · edited Oct 24 '21 at 22:50

0

If this happening on running a React application in Visual Studio Code, please check your propTypes, undefined Proptypes leads to the same issue.

edited Oct 24 '21 at 22:50

Peter Mortensen

30,738
21
105
131

answered Jan 21 '20 at 22:58

kishorekumaru

1,500
2
19
33

score 0 · Answer 33 · answered Feb 28 '20 at 23:25

0

For me I got this error because I lost access to the output path for the dist folder set in my angular.json file. After I reconnected to the remote path with updated credentials the error went away.

answered Feb 28 '20 at 23:25

justTech

25
1
5

score 0 · Answer 34 · edited Oct 24 '21 at 23:06

#!/usr/bin/env node --max-old-space-size=4096 in the ionic-app-scripts.js file didn’t work.

Modifying node_modules/.bin/ionic-app-scripts.cmd by adding

@IF EXIST "%~dp0\node.exe" (
  "%~dp0\node.exe"  "%~dp0\..\@ionic\app-scripts\bin\ionic-app-scripts.js" %*
) ELSE (
  @SETLOCAL
  @SET PATHEXT=%PATHEXT:;.JS;=;%
  node --max_old_space_size=4096  "%~dp0\..\@ionic\app-scripts\bin\ionic-app-scripts.js" %*
)

finally worked.

Sean · Answer 35 · 2022-10-11T20:43:25.140

0

For me, I encountered this problem when running ESLint and Prettier with a large build directory in my React project. After removing it, all things worked.

I guess this is because there are too many files in the build directory.

edited Oct 11 '22 at 20:43

answered Aug 11 '20 at 13:38

Sean

1,055
11
10

score 0 · Answer 36 · edited Oct 24 '21 at 23:25

0

This issue was gone after I've updated my all libraries like, Node.js, TypeScript, Yarn, npm, etc. for my project.

edited Oct 24 '21 at 23:25

Peter Mortensen

30,738
21
105
131

answered Oct 19 '20 at 07:51

Oguzhan Kircali

453
5
11

score 0 · Answer 37 · edited Sep 30 '21 at 12:01

I have a similar issue when I run angular 'ng serve':

"FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory"

In my case I found my Angular application used lazy loading. One module was already imported to itself route module, but someone made an importing it to app module too which caused the recursive(?) loading.

This causes the out of memory.

score 0 · Answer 38 · edited Sep 30 '21 at 12:05

For a non-Angular general JavaScript answer for those who land on this question from Google and want to fix this in your Dockerfile (replace 6144 with the amount of memory in megabytes which you want to allocate).

My implementation was working in Node.js v14.1.0 being executed by Docker version 20.10.5, build 55c4c88 using DockerOperator in airflow v2.0.1).

FROM node:14.1.0

# Create app directory
WORKDIR /tmp/dockerspace/

# Install app dependencies
# A wildcard is used to ensure both package.json AND package-lock.json are copied
COPY package*.json ./

RUN npm install

# Bundle app source
COPY . .

CMD node --max-old-space-size=6144 app.js

score 0 · Answer 39 · edited Oct 24 '21 at 23:35

0

In my case the error was caused by improper use of a condition in a for ... loop. Instead of:

for (let t = startNo; t <= endNo; t++) {}

I had:

for (let t = startNo; endNo; t++) {}

edited Oct 24 '21 at 23:35

Peter Mortensen

30,738
21
105
131

answered Sep 22 '21 at 15:10

Eggon

2,032
2
19
38

score 0 · Answer 40 · edited Jan 18 '22 at 01:17

0

I had the same problem, in my case after of install aws-sdk, not the memory space. I resolved it changing the import to require like this post:

aws-sdk in node app after deploying does not start

edited Jan 18 '22 at 01:17

Dharman

30,962
25
85
135

answered Jan 18 '22 at 01:12

Fredd Hannay

11
1

score 0 · Answer 41 · answered Sep 15 '22 at 09:42

0

For me, it was as silly as module importing itself:

// worker.js
import { worker } from './worker'

answered Sep 15 '22 at 09:42

Nati Kamusher

533
5
9

score 0 · Answer 42 · answered Dec 19 '22 at 15:58

0

In the event this is useful for someone. make sure there is not recursion in our Sass. or non exiting recursion in your recently added code. in some cases max heap exceeded is a sign of this.

answered Dec 19 '22 at 15:58

Cory Lewis

559
5
6

score 0 · Answer 43 · answered Mar 22 '23 at 07:39

0

Try to uninstall node.js. then download again a fresh copy to install.

answered Mar 22 '23 at 07:39

CherryBlossom

393
4
8

score 0 · Answer 44 · answered Jul 01 '23 at 16:55

My problem got solved by using default name in import statement for @mui/icons-material. Dont know how its related to out of memory issue, but now I am running my nextJS project smoothly after this change example, instead of import { Check } from '@mui/icons-material';

I used following format

import CheckIcon from '@mui/icons-material/Check';

score 0 · Answer 45 · answered Jul 04 '23 at 10:08

0

For me, running

yarn cache clean

and

rm -rf node_modules

fixed the memory issue. After this

yarn install

worked fine.

answered Jul 04 '23 at 10:08

PHZ.fi-Pharazon

1,479
14
15

score -10 · Answer 46 · answered Oct 06 '20 at 04:27

-10

Sometimes simplicity is the key to success. Search for while (i <= 10000) {} without increasing i in your code ;)

answered Oct 06 '20 at 04:27

Matthis Kohli

1,877
1
21
23

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory in Ionic 3

46 Answers46

See the current value of max-old-space-size (in MB)

Linked

Related