Closed Bug 1091635 Opened 8 years ago Closed 8 years ago
e10s - Web Content process pins the CPU after killing the UI
When the UI process hangs, and is killed from eg the System Monitor (Ubuntu), the Web Content process tends to go into an infinite loop that takes 100% of one core. The Web Content process needs to be killed separately. Better would be if the Web Content process could discover that its UI process has gone away. I assume this is e10s related. (Ubuntu 14.10.)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.