[Webkit-unassigned] [Bug 174805] New: Eats 100% CPU when starting a new WebProcess fails
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jul 24 17:21:47 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=174805
Bug ID: 174805
Summary: Eats 100% CPU when starting a new WebProcess fails
Product: WebKit
Version: Other
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebKit Gtk
Assignee: webkit-unassigned at lists.webkit.org
Reporter: bugzilla at hadess.net
CC: bugs-noreply at webkitgtk.org
My system was running low on memory, and WebKit likes to precommit tons of memory, so starting a new tab was failing.
Here is epiphany trying to start a new WebProcess 200 times per second, with no feedback except a completely white page.
$ journalctl -b | grep -i epiphany | grep "02:11:56" | wc -l
182
$ journalctl -b | grep -i epiphany | grep "02:11:56" | uniq
Jul 25 02:11:56 classic org.gnome.Epiphany.desktop[24590]: Unable to fork a new WebProcess: Failed to fork (Cannot allocate memory).
I'm not sure whether it's WebKit or epiphany that's responsible for the looping, but an error like when the WebProcess crashes would be useful in that case.
epiphany-3.24.2-1.fc26.x86_64
webkitgtk4-2.16.5-1.fc26.x86_64
--
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/8f09d92a/attachment-0001.html>
More information about the webkit-unassigned
mailing list