[Webkit-unassigned] [Bug 164472] New: GC timers stop to work when Heap claims it grew

[bugzilla-daemon at webkit.org]

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

            Bug ID: 164472
           Summary: GC timers stop to work when Heap claims it grew
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: valkov at yandex.ru

Due to https://bugs.webkit.org/show_bug.cgi?id=151521
when deathRate() now returns 0 (when heap reported that e.g. m_sizeAfterLastEdenCollect > m_sizeBeforeLastEdenCollect or m_sizeAfterLastFullCollect > m_sizeBeforeLastFullCollect after garbage collecting)

GCActivityCallback::didAllocate uses 
    double bytesExpectedToReclaim = static_cast<double>(bytes) * deathRate();
    double newDelay = lastGCLength() / gcTimeSlice(bytesExpectedToReclaim);
    scheduleTimer(newDelay);
which causes newDelay to be positive inf.

GCActivityCallback::scheduleTimer configures the timer to std::chrono::microseconds::max();
and the timer never invoked.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161107/feee7195/attachment.html>