Since updating to 3.3.0, running out of memory
See original GitHub issueDescribe the bug
After upgrading to 3.3.0 and TS 3.7.3 (was previously on 3.2.0 and TS 3.7.2), I am unable to run yarn start
I receive this error: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
Reverting to react-scripts v3.2.0 resolves this issue - Typescript being at 3.7.3 or 3.7.2. has no effect, so I’ve narrowed it to react-scripts.
Did you try recovering your dependencies?
Yes, blew away node_modules and re-ran yarn
, tried without a lock file, etc. No dice.
Environment
Windows 10, VSCode (also occurs on my macbook)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:161
- Comments:133 (9 by maintainers)
Top Results From Across the Web
Critical Error about running out of Memory - WordPress.org
We have noticed that our Woo-commerce is running out of memory every time lately, we currently can't open/edit/update any product page, ...
Read more >Java heap space out of Memory Openhab Release 3.3.0
Hi, After Upgrade to the Release 3.3.0 I constantly get this error after a day or two. ... My system runs out of...
Read more >Getting an out of memory error while using Create React App ...
step 1: split that command up. Try npm i react-plotly. · Based on the last line, the issue is when running npm start...
Read more >1907030 – "dnf update" runs out of memory on swapless ...
4-1.fc29.noarch libdnf-0.22.0-6.fc29.x86_64 And since then it doesn't work on a VM with 512MB RAM (I've tried on all releases F26-F34). It's not aarch64...
Read more >Known Issues | Cribl Docs
Problem: When you teleport from a Leader running v.4.0.1 or 4.0.2 to an Edge ... 2022-12-01 – v.4.0 – Amazon S3 Source stops...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had the same error with nodejs v10; upgrading to nodejs v12 fixed the issue for me.
Temporary workaround is to set a larger max-old-space-size eg,
react-scripts --expose-gc --max-old-space-size=8192 ...
as stated in https://github.com/facebook/create-react-app/issues/8130#issue-535323604