[Webkit-unassigned] [Bug 207931] [macOS] Disable RunLoop function dispatch when there is a pending rendering update

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 19 11:56:22 PST 2020


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

--- Comment #14 from Antti Koivisto <koivisto at iki.fi> ---
> It's kind of scary to allow ourselves to get into a permanently disabled
> state (if someone forgets to make the balancing call to
> setFunctionDispatchSuspended()).
> 
> Instead of a persistent setting, can we make this a one-shot behavior that
> automatically clears itself and then re-schedules a wakeUp()? I believe that
> would be sufficient to allow any scheduled rendering update to complete in
> the current runloop iteration.
> 
> We could call this deferring the next runloop iteration, rather than
> suspending it entirely.

I thought about it. The cost is that we may unnecessarily skip the cycle after the rendering update has already happened (since we won't know if the current one will in fact end up waking up). I'm not sure if that is a problem in practice. Maybe not.

-- 
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/20200219/1581c479/attachment.htm>


More information about the webkit-unassigned mailing list