next.js: FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
Bug report
Describe the bug
If I run the dev server and turn on like few hours. The server automatically shuts down with this error message.
<--- Last few GCs --->
[42587:0x102801e00] 4108743 ms: Mark-sweep 1369.0 (1417.2) -> 1369.0 (1421.2) MB, 558.5 / 0.0 ms allocation failure GC in old space requested
[42587:0x102801e00] 4109472 ms: Mark-sweep 1369.0 (1421.2) -> 1369.0 (1413.2) MB, 729.2 / 0.0 ms last resort GC in old space requested
[42587:0x102801e00] 4109969 ms: Mark-sweep 1369.0 (1413.2) -> 1369.0 (1413.2) MB, 497.1 / 0.0 ms last resort GC in old space requested
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x19c4f6125879 <JSObject>
1: add [/Users/steve/juven/frontend/node_modules/hard-source-webpack-plugin/lib/SerializerAppend2.js:~71] [pc=0x1bb0948a8aa](this=0x19c4e8bde1f9 <WriteOutput map = 0x19c48d594f79>,key=0x19c4e32749c1 <String[61]: 1B2M2Y8AsgTpgAmY7PhCfg==node_modules/rc-animate/es/Animate.js>,content=0x19c4e8bb12e1 <Very long string[308078]>)
2: write [/Users/steve/frontend/node_modules/hard-source-w...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: node::Abort() [/Users/steve/.nvm/versions/node/v8.12.0/bin/node]
2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/Users/steve/.nvm/versions/node/v8.12.0/bin/node]
3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/steve/.nvm/versions/node/v8.12.0/bin/node]
4: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/Users/steve/.nvm/versions/node/v8.12.0/bin/node]
5: v8::internal::String::SlowFlatten(v8::internal::Handle<v8::internal::ConsString>, v8::internal::PretenureFlag) [/Users/steve/.nvm/versions/node/v8.12.0/bin/node]
6: v8::String::WriteUtf8(char*, int, int*, int) const [/Users/steve/.nvm/versions/node/v8.12.0/bin/node]
7: node::StringBytes::Write(v8::Isolate*, char*, unsigned long, v8::Local<v8::Value>, node::encoding, int*) [/Users/steve/.nvm/versions/node/v8.12.0/bin/node]
8: void node::Buffer::(anonymous namespace)::StringWrite<(node::encoding)1>(v8::FunctionCallbackInfo<v8::Value> const&) [/Users/steve/.nvm/versions/node/v8.12.0/bin/node]
9: 0x1bb0710a5c7
10: 0x1bb0948a8aa
error Command failed with signal "SIGABRT".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
To Reproduce
Not sure. Just turn on the dev server for few hours
Expected behavior
Server should not be shut down
Screenshots
If applicable, add screenshots to help explain your problem.
System information
- OS: mac
- Browser chrome
- Version of Next.js: 7.0.0
Additional context
Add any other context about the problem here.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 7
- Comments: 18 (5 by maintainers)
Seeing the same issue. The common node.js solution appears to be using a
flag on the build. How can that flag be injected into the now build?
You can do it by setting NODE_OPTIONS.
ie)
Had to dig through like 40-50 webpages to solve this damn “out of memory” problem and figure out how to give node more memory via npm scripts.
Also going to note, this wasn’t happening on my local macbook (16gb ram). However, kept running into this issue on our jenkin’s t2.medium ec2 instance (only 4gb of ram).
Resources - https://github.com/npm/npm/issues/12238#issuecomment-367147962
You’re welcome codestas’
Happened again in production environment.
@sasindroid happened again. @
^7.0.2Using
"@babel/core": "^7.2.2"and"babel-core": "^7.0.0-bridge.0"and I have a hunch it’s related to babel.It is still happening in Next 9 in both dev and prod. Increasing
max_old_space_sizeis not a solution. Why does node take up so much memory?“Happened again in production environment.” is not really actionable from our side. Please provide a reproduction so that we can investigate.