next.js: OOM on 9.3.6

Bug report

Describe the bug

on a next dev or next build, node runs out of memory.

To Reproduce

run yarn build see this error:

$ next build
$ tsc --project tsconfig.server.json
Warning: Built-in CSS support is being disabled due to custom CSS configuration being detected.
See here for more info: https://err.sh/next.js/built-in-css-disabled

Creating an optimized production build .
<--- Last few GCs --->

[7951:0x108008000]    35387 ms: Mark-sweep 1952.3 (2088.8) -> 1936.1 (2088.0) MB, 313.2 / 0.0 ms  (average mu = 0.157, current mu = 0.070) allocation failure scavenge might not succeed
[7951:0x108008000]    35714 ms: Mark-sweep 1953.8 (2092.3) -> 1938.5 (2090.8) MB, 302.1 / 0.0 ms  (average mu = 0.124, current mu = 0.076) allocation failure scavenge might not succeed


<--- JS stacktrace --->

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

    0: ExitFrame [pc: 0x100931399]
Security context: 0x3c879d1408a1 <JSObject>
    1: add [0x3c879d14ddb9](this=0x3c8743530c61 <Set map = 0x3c87b6fc23c1>,0x3c87663ba029 <Very long string[47196]>)
    2: new Set(aka Set) [0x3c879d14d8a9](this=0x3c8711c80589 <the_hole>,0x3c8793782321 <Set map = 0x3c87b6fc23c1>)
    3: ConstructFrame [pc: 0x1008ad37a]
    4: StubFrame [pc: 0x100991b00]
    5: doResolve [0x3c87f79a1a19] [/...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x10007f4b9 node::Abort() [/.fnm/node-versions/v12.15.0/installation/bin/node]
 2: 0x10007f63d node::OnFatalError(char const*, char const*) [/.fnm/node-versions/v12.15.0/installation/bin/node]
 3: 0x100176a27 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/.fnm/node-versions/v12.15.0/installation/bin/node]
 4: 0x1001769c3 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/.fnm/node-versions/v12.15.0/installation/bin/node]
 5: 0x1002fab75 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/.fnm/node-versions/v12.15.0/installation/bin/node]
 6: 0x1002fc244 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/.fnm/node-versions/v12.15.0/installation/bin/node]
 7: 0x1002f9117 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/.fnm/node-versions/v12.15.0/installation/bin/node]
 8: 0x1002f70fd v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/.fnm/node-versions/v12.15.0/installation/bin/node]
 9: 0x100302814 v8::internal::Heap::AllocateRawWithLightRetry(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/.fnm/node-versions/v12.15.0/installation/bin/node]
10: 0x10030288f v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/.fnm/node-versions/v12.15.0/installation/bin/node]
11: 0x1002ce269 v8::internal::Factory::NewFixedArrayWithFiller(v8::internal::RootIndex, int, v8::internal::Object, v8::internal::AllocationType) [/.fnm/node-versions/v12.15.0/installation/bin/node]
12: 0x100507bab v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Rehash(v8::internal::Isolate*, v8::internal::Handle<v8::internal::OrderedHashSet>, int) [/.fnm/node-versions/v12.15.0/installation/bin/node]
13: 0x1005df0f9 v8::internal::Runtime_SetGrow(int, unsigned long*, v8::internal::Isolate*) [/.fnm/node-versions/v12.15.0/installation/bin/node]
14: 0x100931399 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/.fnm/node-versions/v12.15.0/installation/bin/node]
error Command failed with signal "SIGABRT".

Expected behavior

build runs successfully.

System information

OS: MacOS, ubuntu
Version of Next.js: 9.3.6
Version of Node.js: 12.15.0

Additional context

builds fine with 9.3.5.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 21 (7 by maintainers)

Commits related to this issue

Temporary remove wildcard imports causing infinite loops SEE: https://github.com/zeit/next.js/issues/12280#issuecomment-620706566 FIX: https://github.com/zeit/next.js/pull/12318 — committed to CodeForAfrica/outbreak.AFRICA by kilemensi 4 years ago

Most upvoted comments

Looks like i found a point where it started to fail. It was turning on paths support by default in 9.3.6-canary.3 I don’t know why but I had node_modules in tsconfig paths and it was a problem. So this change made everything work as expected

@VinSpee sorry for not answering questions

Yeah, I can if it’s still actual
Yeah. But I use ts-node only for development purposes (so only next build fails in my case).

zetoke on Apr 28, 2020

So I think the workaround/fix for people can be looking into paths in tsconfig or jsconfig and making sure that it doesn’t have weird stuff as in a previous message.

zetoke on Apr 28, 2020

Opened a PR to fix it: #12318

timneutkens on Apr 29, 2020

I’m super curious why you all had those lines there to begin with, doesn’t seem like it does anything to improve your application.

We’ll figure out a way to make it work though.

timneutkens on Apr 29, 2020

@VinSpee @zetoke feel free to investigate this issue if you’re not going to provide a reproduction. I’d start by downgrading through all canary versions between 9.3.5 and 9.3.6

timneutkens on Apr 28, 2020

@zetoke interesting!

I had this in mine:

    "paths": {
      "*": ["*"],
      …

which, when i changed to

    "paths": {
      "src/*": ["*"],

is now no longer failing. Good eye!

VinSpee on Apr 28, 2020

@timneutkens yeah, it’s a good idea. I will try it out. The challenge with a reproduction is that it’s probably a problem for medium sized projects or bigger and I can’t just opensource the whole project haha. So the way is just to create a lot of dummy pages/components. Probably.

zetoke on Apr 28, 2020

Hi we’d be happy to investigate. But it’s hard to help on this if no reproduction is provided.

timneutkens on Apr 28, 2020