[Bug] JavaScript heap out of memory - allocation failure during execution

Resolved 💬 3 comments Opened Dec 18, 2025 by YanivDudu Closed Dec 22, 2025

Bug Description
<--- Last few GCs --->

[18612:00000200DFB2E000] 71171 ms: Mark-Compact 4022.0 (4137.8) -> 4011.2 (4142.8) MB, pooled: 0 MB, 1875.82 / 0.00 ms (average mu = 0.252, current mu = 0.033) allocation failure; scavenge might not succeed
[18612:00000200DFB2E000] 74268 ms: Mark-Compact 4027.5 (4143.5) -> 4016.7 (4148.3) MB, pooled: 0 MB, 3069.31 / 0.00 ms (average mu = 0.109, current mu = 0.009) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 00007FF71E1570F7 node::SetCppgcReference+18039
2: 00007FF71E0BAA18 v8::base::CPU::num_virtual_address_bits+102920
3: 00007FF71ECBF151 v8::Isolate::ReportExternalAllocationLimitReached+65
4: 00007FF71ECABCD6 v8::Function::Experimental_IsNopFunction+3302
5: 00007FF71EB08420 v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+33904
6: 00007FF71EB04AAA v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+19194
7: 00007FF71EB1B08C v8::Isolate::GetHeapProfiler+8012
8: 00007FF71EB1B90A v8::Isolate::GetHeapProfiler+10186
9: 00007FF71EB2C2FB v8::Isolate::GetHeapProfiler+78267
10: 00007FF71E7F93FB v8::base::AddressSpaceReservation::AddressSpaceReservation+323419
11: 00007FF6BED2D4BA

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.0.72
  • Feedback ID: 68f0b246-3ba8-4143-868b-18ffed28ffca

Errors

[]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗