Closed
Bug 1345108
Opened 7 years ago
Closed 7 years ago
Reduce resolution for timestamp in pingSender's crash pings
Categories
(Toolkit :: Telemetry, defect, P1)
Toolkit
Telemetry
Tracking
()
VERIFIED
FIXED
mozilla55
People
(Reporter: chutten, Assigned: Dexter)
Details
(Whiteboard: [measurement:client])
Attachments
(2 files)
59 bytes,
text/x-review-board-request
|
ted
:
review+
gchang
:
approval-mozilla-aurora+
|
Details |
2.97 KB,
patch
|
Details | Diff | Splinter Review |
While I was writing the patch for bug 1338627 I noticed that, when assembling the crash ping, pingSender uses a per-second-resolution timestamp for creationTimestamp. No big deal, crash manager does the same thing, right? Well, maybe. crash manager's crashping assembly happens at some pseudo-random time in the future, making its creationTimestamp somewhat unrelated to the time that Firefox crashed. pingSender on the other hand runs a far more deterministic time after a crash occurs, making its creationTimestamp somewhat _related_ to the time that Firefox crashed. If, as mentioned in bug 1338627comment#3, we are deliberately trying to be vague about when crashes happened, we should teach pingSender to be vague about its crash pings' creationTimestamps. (by truncating or fuzzing)
Assignee | ||
Updated•7 years ago
|
Priority: -- → P1
Whiteboard: [measurement:client]
Assignee | ||
Comment 1•7 years ago
|
||
The timestamp comes from the crashmanager who builds up the ping, so we should fix it there.
Comment 2•7 years ago
|
||
(In reply to Alessio Placitelli [:Dexter] from comment #1) > The timestamp comes from the crashmanager who builds up the ping, so we > should fix it there. The CrashManager is not affected since it creates the ping at the earliest a minute or two after the crash. The issue is specifically with the crashreporter client that creates a ping only a few instants after the crash happened: https://dxr.mozilla.org/mozilla-central/rev/e03e0c60462c775c7558a1dc9d5cf2076c3cd1f9/toolkit/crashreporter/client/ping.cpp# This causes the ping "creationDate" to be practically the same as the real time of the crash which is a piece of information we don't want to be public.
Updated•7 years ago
|
Summary: Use of high-resolution timestamp in pingSender's crash pings → Reduce resolution for timestamp in pingSender's crash pings
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → alessio.placitelli
Whiteboard: [measurement:client] → [measurement:client][measurement:client:uplift]
Comment hidden (mozreview-request) |
Comment 4•7 years ago
|
||
mozreview-review |
Comment on attachment 8854041 [details] Bug 1345108 - Reduce resolution for timestamp in crashreporter's crash pings. https://reviewboard.mozilla.org/r/126030/#review128654
Attachment #8854041 -
Flags: review?(ted) → review+
Pushed by alessio.placitelli@gmail.com: https://hg.mozilla.org/integration/autoland/rev/7e09e95fef84 Reduce resolution for timestamp in crashreporter's crash pings. r=ted
Assignee | ||
Comment 6•7 years ago
|
||
Comment on attachment 8854041 [details] Bug 1345108 - Reduce resolution for timestamp in crashreporter's crash pings. Approval Request Comment [Feature/Bug causing the regression]: 1310703 [User impact if declined]: Crash pings generated by the crashreporter will report the exact time a crash happened. [Is this code covered by automated tests?]: No [Has the fix been verified in Nightly?]: This will be verified on Nightly as soon as it lands. [Needs manual test from QE? If yes, steps to reproduce]: No [List of other uplifts needed for the feature/fix]: This patch should be applied after bug 1345153 and bug 1348250. [Is the change risky?]: No risk. [Why is the change risky/not risky?]: This is truncating the creationDate string when generating crash pings from the crashreporter, using code that already lived in the crashreporter. [String changes made/needed]: None
Attachment #8854041 -
Flags: approval-mozilla-aurora?
Assignee | ||
Comment 7•7 years ago
|
||
Abe, could you please quickly validate this as soon as it hits Nightly?
Flags: needinfo?(amasresha)
Comment 8•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/7e09e95fef84
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Updated•7 years ago
|
status-firefox54:
--- → affected
Comment 9•7 years ago
|
||
Seems that it doesn't apply to aurora grafting 390651:7e09e95fef84 "Bug 1345108 - Reduce resolution for timestamp in crashreporter's crash pings. r=ted" merging toolkit/components/telemetry/docs/data/crash-ping.rst merging toolkit/crashreporter/client/ping.cpp warning: conflicts while merging toolkit/crashreporter/client/ping.cpp! (edit, then use 'hg resolve --mark') abort: unresolved conflicts, can't continue
Flags: needinfo?(alessio.placitelli)
Assignee | ||
Comment 10•7 years ago
|
||
Rebased patch. Is it ok to uplift this?
Flags: needinfo?(alessio.placitelli) → needinfo?(sledru)
Comment 11•7 years ago
|
||
QE Verified as fixed. Test cases and runs are available here: https://public.etherpad-mozilla.org/p/_Bug_1345108
Status: RESOLVED → VERIFIED
Flags: needinfo?(amasresha)
Comment 12•7 years ago
|
||
Comment on attachment 8854041 [details] Bug 1345108 - Reduce resolution for timestamp in crashreporter's crash pings. Fix timestamp in crash pings and was verified. Aurora54+.
Attachment #8854041 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Updated•7 years ago
|
Flags: needinfo?(sledru)
Comment 13•7 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-aurora/rev/a213b5ee1fba
Assignee | ||
Updated•7 years ago
|
Whiteboard: [measurement:client][measurement:client:uplift] → [measurement:client]
You need to log in
before you can comment on or make changes to this bug.
Description
•