Closed
Bug 1677321
Opened 4 years ago
Closed 3 years ago
Idle time on Gecko_IOThread and Chrome_ChildThread should be annotated as idle for the profiler
Categories
(Core :: IPC, enhancement)
Core
IPC
Tracking
()
RESOLVED
FIXED
85 Branch
| Tracking | Status | |
|---|---|---|
| firefox85 | --- | fixed |
People
(Reporter: mstange, Assigned: mstange)
References
Details
Attachments
(1 file)
Profile: https://share.firefox.dev/32LN4oK
The two threads in question have a fully grey graph, even though they're mostly idle.
|
Assignee | |
Comment 1•4 years ago
|
||
Profile with patch: https://share.firefox.dev/2UoXs1b
|
|
Assignee | |
Comment 2•4 years ago
|
||
|
||
Comment 4•4 years ago
|
||
Incidentally, back when I filed bug 1489604 I was also thinking of renaming the threads to something more obvious to make them easier to select in the profiler, like IPC I/O Parent and IPC I/O Child, but I don't know if I ever filed a bug for it.
Pushed by mstange@themasta.com: https://hg.mozilla.org/integration/autoland/rev/305240dee390 Annotate the idle stack in MessagePumpLibevent::Run with the profiler IDLE category. r=jld
|
||
Comment 6•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox85:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•