Dev server exits often (JavaScript heap out of memory)
See original GitHub issueWhile working with my glimmer app (development), my dev server exits with the following error more often.
<--- Last few GCs --->
5154518 ms: Mark-sweep 1303.9 (1435.5) -> 1297.8 (1435.5) MB, 975.6 / 0.0 ms [allocation failure] [GC in old space requested].
5155519 ms: Mark-sweep 1297.8 (1435.5) -> 1297.5 (1435.5) MB, 1000.6 / 0.0 ms [allocation failure] [GC in old space requested].
5156538 ms: Mark-sweep 1297.5 (1435.5) -> 1300.1 (1412.5) MB, 1017.6 / 0.0 ms [last resort gc].
5157597 ms: Mark-sweep 1300.1 (1412.5) -> 1302.5 (1412.5) MB, 1059.7 / 0.0 ms [last resort gc].
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x13366fbcfb39 <JS Object>
1: DoJoin(aka DoJoin) [native array.js:~129] [pc=0x2ffe5997c286] (this=0x13366fb04381 <undefined>,w=0x8f323781e29 <JS Array[105]>,x=105,N=0x13366fb043c1 <true>,J=0x13366fb04411 <String[0]: >,I=0x13366fbb46c9 <JS Function ConvertToString (SharedFunctionInfo 0x13366fb52dc9)>)
2: Join(aka Join) [native array.js:180] [pc=0x2ffe597a60f2] (this=0x13366fb04381 <undefined>,w=0x8f323781e29 <JS A...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: node::Abort() [/Users/gokul-3858/.nvm/versions/node/v6.10.3/bin/node]
2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/Users/gokul-3858/.nvm/versions/node/v6.10.3/bin/node]
3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/gokul-3858/.nvm/versions/node/v6.10.3/bin/node]
4: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/Users/gokul-3858/.nvm/versions/node/v6.10.3/bin/node]
5: v8::internal::Runtime_StringBuilderConcat(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/gokul-3858/.nvm/versions/node/v6.10.3/bin/node]
6: 0x2ffe569092a7
7: 0x2ffe5997c286
8: 0x2ffe597a60f2
Abort trap: 6
and my deps are,
"@glimmer/application": "^0.8.0",
"@glimmer/application-pipeline": "^0.9.0",
"@glimmer/blueprint": "~0.6.4",
"@glimmer/component": "^0.8.0",
Any help? Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
webpack-dev-server and JavaScript heap out of memory
I recently upgraded from webpack 3 to 4 and started running into this issue fairly often, whereas before I never encountered this at...
Read more >How to Fix JavaScript Heap Out of Memory Error
This error usually occurs when the default memory allocated by your system to Node. js is not enough to run a large project....
Read more >JavaScript Heap Out Of Memory Error
A quick solution that you can use to fix "Heap Out Of Memory Error" in JavaScript. We lay out the causes and how...
Read more >Node.js heap out of memory - javascript
After running this i type npm run dev and it stopped there. it is not showing any progress not giving any error after...
Read more >Resolving Out-of-Memory Issues
The default node process in node >= 12 has a 2GB “heap size” allocated for memory. It's plausible that you could increase memory...
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 Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

will try to reproduce in a different repo @rwjblue. However, its occuring on my every dev serve 🤕
Closing due to inactivity. Please re-open if you still encounter the problem and have a reproduction!