[Webkit-unassigned] [Bug 65382] The JSC garbage collector returns memory to the operating system too eagerly

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jul 3 09:41:33 PDT 2012


--- Comment #19 from Filip Pizlo <fpizlo at apple.com>  2012-07-03 09:41:32 PST ---
(In reply to comment #18)
> (From update of attachment 102454 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=102454&action=review
> > Source/JavaScriptCore/heap/Heap.cpp:334
> > +        // Generally wait for one second before scavenging free blocks. This
> > +        // may return early, particularly when we're being asked to quit.
> > +        waitForRelativeTime(1.0);
> Filip, is there any special reason for this one second timeout? Can it be 10 seconds for example? Or infinite?

Not really.  It's the answer to the question: "how long after I stop doing stuff in my browser do I expect my browser to return memory to the OS?"

Shortening this timeout will slow things down because the block freeing thread would then contend on the allocation mutex more frequently.

Lengthening the timeout may cause other applications to experience longer periods of memory starvation while the browser hoards memory.

One second feels like the right compromise.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list