Closed
Bug 708674
Opened 13 years ago
Closed 12 years ago
Add telemetry probe for Firefox shutdown
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
INVALID
People
(Reporter: lmandel, Assigned: andreshm)
References
Details
(Whiteboard: [Snappy:p3] [Telemetry])
Attachments
(1 file)
3.58 KB,
patch
|
Gavin
:
feedback-
|
Details | Diff | Splinter Review |
As requested by product (see https://etherpad.mozilla.org/desktop-responsiveness) add a telemetry probe for Firefox shutdown: from close to visual disappearance to process exited fully.
Updated•13 years ago
|
Component: Telemetry → General
Product: Toolkit → Firefox
QA Contact: telemetry → general
Updated•13 years ago
|
Whiteboard: [Snappy] [Telemetry] → [Snappy:p3] [Telemetry]
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → andres
Assignee | ||
Comment 1•12 years ago
|
||
First I tried with observers, but that's not going to work, since telemetry classes are shutdown before the stopwatch should finish.
However, the nsAppStartup already store in a profile file (Telemetry.ShutdownTime.txt) the last shutdown time. So, I'm reading that file and adding the value to a telemetry. But, I'm not sure where this should happen. I'm temporally using nsBrowserGlue.js, but I need some advice on this.
Attachment #666067 -
Flags: feedback?(gavin.sharp)
Comment 2•12 years ago
|
||
Comment on attachment 666067 [details] [diff] [review]
Patch v1
This information is already sent in the telemetry ping explicitly (that's why this file was added to begin with):
http://hg.mozilla.org/mozilla-central/annotate/ed5f37774104/toolkit/components/telemetry/TelemetryPing.js#l141
I think that means there's nothing left to do here.
Attachment #666067 -
Flags: feedback?(gavin.sharp) → feedback-
Assignee | ||
Comment 3•12 years ago
|
||
:O that makes sense. How this bug should be resolved, as WONTFIX?
Comment 4•12 years ago
|
||
Let's go with INVALID, someone can reopen if the existing shutdown telemetry isn't sufficient.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 5•12 years ago
|
||
I don't think this bug was invalid when filed as I'm pretty sure shutdown Telemetry didn't exist at that point in time. However, I do agree that the bug should be resolved at this point.
You need to log in
before you can comment on or make changes to this bug.
Description
•