[Webkit-unassigned] [Bug 233980] A dedicated worker is not frozen even when the page is in back/forward cache

[bugzilla-daemon at webkit.org]

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

Yusuke Suzuki <ysuzuki at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ysuzuki at apple.com

--- Comment #9 from Yusuke Suzuki <ysuzuki at apple.com> ---
(In reply to Chris Dumez from comment #5)
> (In reply to Alexey Proskuryakov from comment #4)
> > Would it suspend threads holding mutexes, and freeze the main thread as a
> > consequence?
> 
> You're right, I think that would be a risk indeed and very likely the reason
> why our suspension logic currently works the way it does.
> 
> I guess timeout + kill is the way to go then.

Yes. One example is that malloc can have a global mutex for the slow path (e.g. stealing a page from the global heap instead of thread local heap). If we suspend a thread holding that mutex, most likely, soon, the other threads will be blocked once malloc happens.

-- 
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/20211209/86d46cc8/attachment.htm>