[Webkit-unassigned] [Bug 174805] [GTK][WPE] Eats 100% CPU when starting a new WebProcess fails

[bugzilla-daemon at webkit.org]

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

Michael Catanzaro <mcatanzaro at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mcatanzaro at igalia.com
            Summary|Eats 100% CPU when starting |[GTK][WPE] Eats 100% CPU
                   |a new WebProcess fails      |when starting a new
                   |                            |WebProcess fails

--- Comment #1 from Michael Catanzaro <mcatanzaro at igalia.com> ---
We need some general limit on how many times the web process can be launched in a row. If it's failed to launch, say, five times in under one second, it's time to just give up. This is really unfortunate, as there's no way to report an error if we can't display an error page in the web process. In this case, I'd say it's sufficiently-fatal that the UI process should probably crash with SIGABRT or something.

We also need to do way better with how we handle OOM situations -- we shouldn't be creating a new web process at all in that case -- but that's a separate issue. (Fixing that is actually on our mid-term roadmap now.)

-- 
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/20170725/255ea448/attachment.html>