Nuxt.js: Out of memory error building with new nuxt-edge 2.0.0-25465851.937ce61

[pbastowski]

Hi

My system:

MacBook Pro 15
16gb memory
macOs High Sierra
Node version 9.11.1

I have an express app that uses Nuxt as the last middleware. With version 2.0.0-25452542.7f9d16c (dated 2018-05-24) my app was compiling and running successfully.

With the latest version 2.0.0-25465851.937ce61 (dated 2018-06-02) it crashes with the error below.

● client █████████████████████████ building modules (24%) 120/132 modules 12 act
ive
  node_modules/core-js/library/modules/_iter-define.js

#
# Fatal error in , line 0
# API fatal error handler returned after process out of memory
#

Used memory at crash time 9.45 GB out of 16GB

_{This question is available on Nuxt.js community (#c7196)}

[aldarund]

@pbastowski try to remove node_modules and lock files and install from new.

[pbastowski]

@aldarund Just tried that with the latest

"nuxt-edge": "2.0.0-25471736.3b2ed03",

Same result.

#
# Fatal error in , line 0
# 

#
# Fatal error in , line 0
# 

#
# Fatal error in , line 0
# API fatal error handler returned after process out of memoryAPI fatal error handler returned after process out of memoryAPI fatal error handler returned after process out of memory
#

Something was introduced since version 2.0.0-25452542.7f9d16c, the last version that works for me, which is causing this.

[pi0]

@pbastowski A simple reproduction repo would be much appreciated.

BTW I think this might be with postcss-preset-env

[pbastowski]

@pi0 I was thinking about creating a repro. I think you must have read my mind :)
Is there any way I could have a chat with you one on one?

[pi0]

@pbastowski You can contact me via (pyapar at gmail)

[pbastowski]

@pi0 I tried the latest version and I'm still getting the out of memory errors, as per below. I'm stuck on the older version 2.0.0-25452542.7f9d16c from 25 May.

● client █████████████████████████ building modules (43%) 277/315 modules 38 active
  ../frontend/node_modules/core-js/modules/es7.set.of.js

● server █████████████████████████ building modules (25%) 127/131 modules 4 active
  babel-loader › vue-loader › ../frontend/src/app/sofy-filter-drawer.vue

<--- Last few GCs --->

[42115:0x103001400]    84572 ms: Mark-sweep 1782.7 (1856.7) -> 1782.2 (1867.7) MB, 1006.8 / 0.0 ms  allocation failure GC in old space requested
[42115:0x103001400]    85587 ms: Mark-sweep 1782.2 (1867.7) -> 1782.0 (1837.2) MB, 1014.6 / 0.0 ms  last resort GC in old space requested
[42115:0x103001400]    86591 ms: Mark-sweep 1782.0 (1837.2) -> 1782.0 (1837.2) MB, 1003.0 / 0.0 ms  last resort GC in old space requested


<--- JS stacktrace --->

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

Security context: 0x269bc6da55e9 <JSObject>
    1: tokenize(aka tokenize) [/Users/paul/dev/kpmg/SOFY2/frontend/node_modules/postcss-attribute-case-insensitive/node_modules/postcss-selector-parser/dist/tokenize.js:~86] [pc=0x1e50b405ac09](this=0x269be2d822d1 <undefined>,input=0x269b67808c39 <Object map = 0x269b7a88b159>)
    2: new Parser [/Users/paul/dev/kpmg/SOFY2/frontend/node_modules/postcss-attribute-case-insensitive/node_modules/post...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/usr/local/bin/node]
 2: node::FatalTryCatch::~FatalTryCatch() [/usr/local/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
 4: v8::internal::Factory::NewUninitializedFixedArray(int) [/usr/local/bin/node]
 5: v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastPackedObjectElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)2> >::GrowCapacity(v8::internal::Handle<v8::internal::JSObject>, unsigned int) [/usr/local/bin/node]
 6: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
 7: 0x1e50b39842fd

[pbastowski]

The problem has resolved itself with the latest build.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.