Closed
Bug 1488523
Opened 7 years ago
Closed 7 years ago
Annotate crash reports if web replay is running
Categories
(Core Graveyard :: Web Replay, enhancement)
Core Graveyard
Web Replay
Tracking
(firefox64 fixed)
RESOLVED
FIXED
mozilla64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: mccr8, Assigned: bhackett1024)
References
Details
Attachments
(2 files)
|
1.18 KB,
patch
|
gsvelto
:
review+
|
Details | Diff | Splinter Review |
|
3.13 KB,
patch
|
gsvelto
:
review+
|
Details | Diff | Splinter Review |
It won't always be apparent if a crash happened in a process that is recording or replaying. By adding an annotation if we are recording/replaying, maybe it will be easier to tell when a new crash only happens then. (Of course, crashes that happen normally can also happen during recording/replaying.)
| Assignee | ||
Updated•7 years ago
|
Assignee: nobody → bhackett1024
| Assignee | ||
Comment 1•7 years ago
|
||
Add a RecordReplay crash annotation that is always set for reports in middleman or recording/replaying processes.
Attachment #9006666 -
Flags: review?(gsvelto)
| Assignee | ||
Comment 2•7 years ago
|
||
By itself, the patch in part 1 doesn't do anything. The annotation is added before the crash reporter client is initialized, so a delayed note is generated instead. Unfortunately, at this point in startup the delayed notes have already been processed. The basic problem seems to be that the delayed notes are processed when the remote exception handler is initialized, when they are actually contingent on the crash reporter client existing.
Attachment #9006667 -
Flags: review?(gsvelto)
| Reporter | ||
Comment 3•7 years ago
|
||
You'll also want to file a bug against Soccoro that will make it so that the value is publicly queryable and can be used as a column in searches, etc. I'm not sure on the specifics, but somebody who works on that stuff should be able to figure it out.
Comment 4•7 years ago
|
||
Comment on attachment 9006666 [details] [diff] [review]
Part 1 - Add RecordReplay crash annotation.
Review of attachment 9006666 [details] [diff] [review]:
-----------------------------------------------------------------
::: toolkit/crashreporter/CrashAnnotations.yaml
@@ +579,5 @@
> type: string
>
> +RecordReplay:
> + description: >
> + Set to "true" if this crash happened in a Web Replay middleman, recording,
nit: booleans in crash annotations translate to 1 for true and 0 or absent for false, while this is a little awkward it's better to stick to the existing convention. Change this bit of the description from "true" to 1 like in other boolean entries.
Attachment #9006666 -
Flags: review?(gsvelto) → review+
Comment 5•7 years ago
|
||
Comment on attachment 9006667 [details] [diff] [review]
Part 2 - Don't drop delayed crash annotations at startup.
Review of attachment 9006667 [details] [diff] [review]:
-----------------------------------------------------------------
Ouch, I never noticed this was the case, thanks for fixing this.
Attachment #9006667 -
Flags: review?(gsvelto) → review+
Pushed by bhackett@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/65a6efaed937
Part 1 - Add RecordReplay crash annotation, r=gsvelto.
https://hg.mozilla.org/integration/mozilla-inbound/rev/d5663441ffe0
Part 2 - Don't drop delayed crash annotations at startup, r=gsvelto.
Comment 7•7 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/65a6efaed937
https://hg.mozilla.org/mozilla-central/rev/d5663441ffe0
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•