[Webkit-unassigned] [Bug 141820] New: If RunLoop::performWork() doesn't clear the m_functionQueue, maybe we should re-signal the runloop source

[bugzilla-daemon at webkit.org]

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

            Bug ID: 141820
           Summary: If RunLoop::performWork() doesn't clear the
                    m_functionQueue, maybe we should re-signal the runloop
                    source
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: simon.fraser at apple.com

It's possible for RunLoop::performWork() to return without handling all the functions in the queue. In that case, CF is going to unset the CFRunLoopSource "signaled" state, which means that source won't get processed again until RunLoop::dispatch is called.

We should re-signal the source at the end of RunLoop::performWork() if there's still work to do. This is OK, because CF unsets the signaled bit before it calls us.

Also, RunLoop::dispatch() should drop the mutex before calling wakeUp().

-- 
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/20150220/de4aa1b7/attachment-0002.html>