Closed
Bug 1322467
Opened 8 years ago
Closed 3 years ago
Sometimes the profiler randomly stops profiling the content process
Categories
(Core :: Gecko Profiler, defect, P3)
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox53 | --- | affected |
People
(Reporter: mstange, Unassigned)
References
(Blocks 1 open bug)
Details
If I have a session with multiple tabs open for a long time, getting the profile sometimes doesn't contain a content process profile.
Is this still happening?
In any case, the profiler could probably record information about processes it knows about during a profiling session, so that if any goes missing at the end, a message could be added (maybe in the extra log from bug 1676271), to be shown on the frontend.
Severity: normal → N/A
Priority: -- → P3
|
||
Comment 2•3 years ago
|
||
Likely fixed by the work done in bug 1673513.
I was hoping so! Alright, I'll mark this bug fixed, please reopen if it happens again...
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•