[Webkit-unassigned] [Bug 262290] New: Expose a way to report when extra memory in old region has increased in size

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 28 02:04:50 PDT 2023


            Bug ID: 262290
           Summary: Expose a way to report when extra memory in old region
                    has increased in size
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jarred at jarredsumner.com

Say you have a long-running task that writes to dynamically-sized non-GC'd buffers. Those buffers may increase in size after the parent cell moves from eden -> old space. This size increase would not be reported to the GC, causing extra memory to be under-reported to the GC.

The pattern of calling Heap::reportExtraMemoryAllocated and Heap::reportExtraMemoryVisited doesn't quite work for this case because the allocated size is dynamic.

Concrete example: streaming an HTTP response body. Each write from JS might have a delay and might need to be buffered. If the buffer doesn't have enough space, the buffer will grow, but the memory growth won't be reported to the garbage collector since the memory growth happened in native code after the initial allocation.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230928/08a1e4d5/attachment-0001.htm>

More information about the webkit-unassigned mailing list