Closed
Bug 519882
Opened 16 years ago
Closed 16 years ago
Display install_age field on report page
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
VERIFIED
FIXED
1.7
People
(Reporter: Dolske, Assigned: ozten)
Details
Attachments
(1 file)
|
9.03 KB,
patch
|
ryansnyder
:
review+
laura
:
review+
|
Details | Diff | Splinter Review |
In bug 519340 I've noticed a sudden recent spike in a particular type of crash, which seems to happen during startup.
It might be useful if we knew when the user had updated to the version of Firefox they're running, relative to the crash time. If they have been using this version of Firefox for a long time, then the sudden onset of a crash would imply something else on their system changed. [Or it's been there all along, but presumably a 100% reproducible crash-on-startup bug would quickly make people switch to another browser or find a fix.]
I know there's also been interest in looking at crash trends vs. day-of-release, so this data might help refine that to crash trends vs. day-of-user-install.
Side note: The last-update time should probably only have a 1-day granularity, to eliminate concerns about user tracking. [A million or so users install Firefox on any given day, whereas any given microsecond probably only has 1 person installing Firefox.]
Comment 1•16 years ago
|
||
We currently send a "InstallTime" variable that is defined as "time the version with this Build ID was first run" (this was implemented in bug 376720):
http://mxr.mozilla.org/mozilla-central/source/toolkit/crashreporter/nsExceptionHandler.cpp#614
I guess we're not displaying that data currently, since we're definitely storing it:
http://code.google.com/p/socorro/source/browse/trunk/socorro/processor/processor.py#661
Over to Socorro to get the data displayed.
Component: Breakpad Integration → Socorro
Product: Toolkit → Webtools
QA Contact: breakpad.integration → socorro
Updated•16 years ago
|
Summary: Include time of last Firefox update in crash reports → Display install_age field on report page
Comment 2•16 years ago
|
||
Note that Socorro does the math, taking "Crash Time" - "Install Time", and storing the difference as "install_age", which is more useful anyway.
Comment 3•16 years ago
|
||
This should be pretty quick. Austin, can you add this?
Assignee: nobody → ozten.bugs
Severity: normal → trivial
Target Milestone: --- → 1.7
| Assignee | ||
Comment 4•16 years ago
|
||
Wanted to do something lightweight to make the number of seconds useful, without going crazy and implementing Ruby On Rails "distance_of_time_in_words" in php.
Attachment #444791 -
Flags: review?(ryan)
Attachment #444791 -
Flags: review?(laura)
Comment 5•16 years ago
|
||
Comment on attachment 444791 [details] [diff] [review]
Adds install_age to report/index. Display's a rough estimate of relative time to be helpful.
Looks good to me.
Attachment #444791 -
Flags: review?(ryan) → review+
| Assignee | ||
Comment 6•16 years ago
|
||
Sending webapp-php/application/libraries/timeutil.php
Sending webapp-php/application/views/report/index.php
Sending webapp-php/tests/TimeUtilTest.php
Transmitting file data ...
Committed revision 2064.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 8•16 years ago
|
||
Comment on attachment 444791 [details] [diff] [review]
Adds install_age to report/index. Display's a rough estimate of relative time to be helpful.
I guess you don't need review from me, but this looks good (and I am easily amused by the function name).
Attachment #444791 -
Flags: review?(laura) → review+
Updated•14 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•