On Wed, Dec 3, 2025 at 4:03 PM 'Mati Cohen' via v8-users <[email protected]> wrote: > > Hey, > > After building 14.0.365.4, my app is now experiencing some > FatalProcessOutOfMemory when recomputing limits. > > Here is the stack trace > > #00 pc 0x1327140 (v8::base::OS::Abort()) > #01 pc 0x132a898 (v8::base::FatalOOM(v8::base::OOMType, char const*)) > #02 pc 0x1337790 > (v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char > const*, v8::OOMDetails const&)) > #03 pc 0x15147fc (v8::internal::Heap::FatalProcessOutOfMemory(char const*)) > #04 pc 0x1517b6c > (v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector, > v8::base::TimeTicks)) > #05 pc 0x152e484 > (v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, > v8::internal::GarbageCollectionReason, v8::GCCallbackFlags, > v8::internal::PerformHeapLimitCheck)::$_1::operator()() const) > #06 pc 0x152ddc0 (void > heap::base::Stack::SetMarkerAndCallbackImpl<v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, > v8::internal::GarbageCollectionReason, v8::GCCallbackFlags, > v8::internal::PerformHeapLimitCheck)::$_1>(heap::base::Stack*, void*, void > const*)) > #07 pc 0x1e15700 (PushAllRegistersAndIterateStack) > > I had to build with cppgc_enable_pointer_compression and > cppgc_enable_caged_heap set to false due to crashes when reserving space for > pointer compression cage for Oilpan. > > Any insight? Thanks!
What was the error message? If it's "Ineffective mark-compacts near heap limit", add a NearHeapLimitCallback that increases the heap limit. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/v8-users/CAHQurc8GS6vWGLzjs3%2BXmu2R-pOxpyLMmj_6Mc%2B19%3D3k4WS2cA%40mail.gmail.com.
