[Webkit-unassigned] [Bug 45186] Use the Windows thread pool instead of an extra thread for FastMalloc scavenging

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=45186





--- Comment #9 from Adam Roben (aroben) <aroben at apple.com>  2011-01-14 10:52:59 PST ---
(From update of attachment 78538)
View in context: https://bugs.webkit.org/attachment.cgi?id=78538&action=review

>> Source/JavaScriptCore/wtf/FastMalloc.cpp:1536
>> +}
> 
> It would be nice if we could share a little more of the logic in signalScavenger(). Adding some new functions like isScavengerScheduled() (or its opposite, isScavengerSuspended()) and scheduleScavenger() should make that pretty easy.

I don't think there's anything that prevents m_scavengeQueueTimer from firing again if periodicScavenge is taking a long time. Maybe we should always use a non-repeating timer and delete it every time it fires?

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