Closed
Bug 1411818
Opened 8 years ago
Closed 5 years ago
New tabs refuse to load, appear blank white, due to bad content process at 100% CPU (83% in js::gc::GCRuntime::gcCycle)
Categories
(Core :: JavaScript: GC, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jib, Unassigned)
Details
Attachments
(1 file)
|
27.38 KB,
text/plain
|
Details |
I keep running into this symptom occasionally, recall seeing it when Nightly was 57 too. Saw it again just now in Nightly (58):
Suddenly, tabs I open stop responding to having urls entered. The content area just clears and goes blank white when I hit enter. The chrome still works, just nothing shows up on the page, or even looks like it's trying. I can type in any url I want, but content appears dead.
Only some tabs are affected, and they're all are of the same content process. Looking at Activity Monitor shows that content process at ~107% (it's OSX).
So this time I did a 30 second profile of that process to see where that time is spent.
Attached is a cut'n'paste text file of the output (full profile available on request). To summarize:
83.1% is spent in mozilla::dom::TabChild::RecvRealMouseButtonEvent, which in turn ends up in
56.7% js::gc::GCRuntime::gcCycle
The remaining
26.4% is spent in mozilla::EventStateManager::DispatchMouseOrPointerEvent, also in
26.4% js::gc::GCRuntime::gcCycle
So basically, GC/CC run amok enough to make this content process unresponsive to anything else.
I can't reliably repro, so hopefully these are clues.
I didn't get to try closing any tabs to see if it would help, as the content process crashed shortly after the trace. See bp-dc63b173-6903-4747-a8a4-0ddfe0171026
| Reporter | ||
Updated•8 years ago
|
status-firefox57:
--- → affected
Comment 1•8 years ago
|
||
I have also seen this occasionally happen on my OSX machine. It's impossible to reliably reproduce for me.
Comment 2•7 years ago
|
||
status-firefox59:
--- → ?
Updated•6 years ago
|
Component: General → DOM: Content Processes
Product: Firefox → Core
Comment 3•5 years ago
|
||
So basically, GC/CC run amok enough to make this content process unresponsive to anything else.
moving to GC component
Component: DOM: Content Processes → JavaScript: GC
Summary: New tabs refuse to load, appear blank white, due to bad content process at 100% CPU → New tabs refuse to load, appear blank white, due to bad content process at 100% CPU (83% in js::gc::GCRuntime::gcCycle)
Comment 4•5 years ago
|
||
I don't think there's enough to go on here.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•