Javascript heap out of memory

After updating to Alpha-117 I am recieving frequent javascript heap out of memory.

```
<--- Last few GCs --->

[360899:0x13a17000] 150817 ms: Mark-Compact 4046.8 (4134.5) -> 4039.4 (4143.0) MB, pooled: 0 MB, 1525.02 / 0.00 ms (average mu = 0.233, current mu = 0.157) allocation failure; scavenge might not succeed
[360899:0x13a17000] 153007 ms: Mark-Compact 4051.4 (4144.0) -> 4045.3 (4149.0) MB, pooled: 0 MB, 1941.98 / 0.00 ms (average mu = 0.167, current mu = 0.113) allocation failure; GC in old space requested

<--- JS stacktrace --->

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

1: 0xe13fde node::OOMErrorHandler(char const*, v8::OOMDetails const&) [claude]
2: 0x11d5070 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [claude]
3: 0x11d5347 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [claude]
4: 0x1402c05 [claude]
5: 0x141c499 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [claude]
6: 0x13f0b48 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [claude]
7: 0x13f1a75 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [claude]
8: 0x13ca74e v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [claude]
9: 0x182bef0 v8::internal::Runtime_AllocateInOldGeneration(int, unsigned long*, v8::internal::Isolate*) [claude]
10: 0x7f8cabeac476
```

No files, tests, or entry points are named. Start by reproducing the JavaScript heap out-of-memory failure after updating to Alpha-117, then compare memory behavior with the previous version using the provided Node.js error output. Done means the same workload no longer exhausts the heap, with a regression test or reproducible verification added where the relevant entry point is found.

Written by the indexing model from the issue text.