-
Notifications
You must be signed in to change notification settings - Fork 29.1k
Open
Labels
RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.
Description
Link to the code that reproduces this issue
https://github.com/NeoSahadeo/Avg-NextJS-experience
To Reproduce
- run pnpm run dev or pnpm next dev
Current vs. Expected behavior
Expected:
<--- Last few GCs --->
[3314:0xde692d0] 178177 ms: Scavenge 2024.1 (2060.6) -> 2016.6 (2060.6) MB, 4.90 / 0.00 ms (average mu = 0.692, current mu = 0.515) allocation failure;
[3314:0xde692d0] 178198 ms: Scavenge 2024.3 (2060.6) -> 2016.7 (2060.8) MB, 4.67 / 0.00 ms (average mu = 0.692, current mu = 0.515) allocation failure;
[3314:0xde692d0] 181163 ms: Mark-Compact 2617.4 (2653.9) -> 2214.5 (2274.8) MB, 2633.36 / 0.00 ms (average mu = 0.565, current mu = 0.404) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb8cf03 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
2: 0xf04610 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
3: 0xf048f7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
4: 0x1116545 [node]
5: 0x112e3c8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
6: 0x11044e1 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
7: 0x1105675 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
8: 0x10e2cc6 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
9: 0x153e806 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
10: 0x7f0d36e99ef6
<--- Last few GCs --->
[4029:0x19bec2d0] 182670 ms: Scavenge 2017.4 (2046.8) -> 2016.5 (2047.1) MB, 1.96 / 0.00 ms (average mu = 0.603, current mu = 0.443) allocation failure;
[4029:0x19bec2d0] 182676 ms: Scavenge 2017.5 (2047.1) -> 2016.5 (2047.1) MB, 5.03 / 0.00 ms (average mu = 0.603, current mu = 0.443) allocation failure;
[4029:0x19bec2d0] 184729 ms: Mark-Compact 2610.5 (2640.1) -> 2214.1 (2244.8) MB, 1737.89 / 0.00 ms (average mu = 0.444, current mu = 0.171) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb8cf03 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
2: 0xf04610 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
3: 0xf048f7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
4: 0x1116545 [node]
5: 0x112e3c8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
6: 0x11044e1 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
7: 0x1105675 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
8: 0x10e220a v8::internal::Factory::AllocateRawWithAllocationSite(v8::internal::Handle<v8::internal::Map>, v8::internal::AllocationType, v8::internal::Handle<v8::internal::AllocationSite>) [node]
9: 0x10ef6a8 v8::internal::Factory::NewJSObjectFromMap(v8::internal::Handle<v8::internal::Map>, v8::internal::AllocationType, v8::internal::Handle<v8::internal::AllocationSite>) [node]
10: 0x134b2bf v8::internal::JSObject::New(v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Handle<v8::internal::JSReceiver>, v8::internal::Handle<v8::internal::AllocationSite>) [node]
11: 0x1358546 v8::internal::JSDate::New(v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Handle<v8::internal::JSReceiver>, double) [node]
12: 0xf8b430 v8::internal::Builtin_DateConstructor(int, unsigned long*, v8::internal::Isolate*) [node]
13: 0x1977df6 [node]
ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Command was killed with SIGABRT (Aborted): next dev
Provide environment information
next info crashes.
System info:
Host: 82H8 IdeaPad 3 15ITL6
Kernel: 6.15.9-zen1-1-zen
Uptime: 12 mins
Packages: 2352 (pacman), 48 (flatpak)
Shell: bash 5.3.3
Resolution: 1920x1080
DE: Hyprland
Terminal: alacritty
CPU: 11th Gen Intel i3-1115G4 (4) @ 4.100GHz
GPU: Intel Tiger Lake-LP GT2 [UHD Graphics G4]
Memory: 4144MiB / 11738MiB
Binaries:
node version: v20.19.2 (I tried using 18.18 with the same result)
pnpm version: 10.14.0
npm version: 10.8.2
Which area(s) are affected? (Select all that apply)
Runtime
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
I believe that I used Nextjs roughly a month ago to setup a project and it ran just fine. Unfortunately I do not have the project with me. next v14.2.31
works just fine.
moy-kanal-17
Metadata
Metadata
Assignees
Labels
RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.