Closed
Bug 1502534
Opened 6 years ago
Closed 6 years ago
Crash pings don't have sessionIds for child process crashes
Categories
(Toolkit :: Crash Reporting, enhancement)
Tracking
()
RESOLVED
FIXED
mozilla65
Tracking | Status | |
---|---|---|
firefox65 | --- | fixed |
People
(Reporter: tdsmith, Assigned: gsvelto)
References
Details
Attachments
(1 file)
The `payload.sessionId` field of a crash ping seems to be missing when the processType is not "main". It would be useful to report sessionIds for child process crashes if they're available.
The instant use case is that we want to exclude all crashes from the first telemetry session after a user enrolls in the WebRender experiment, since WebRender won't be deactivated for the "disabled" branch until the browser is restarted.
Flags: needinfo?(wlachance)
Comment 1•6 years ago
|
||
Was hoping this would have an obvious answer that I could dig up myself, but my brief spelunking in the crashreporter code didn't turn up anything.
It doesn't seem like the property is explicitly blacklisted as an annotation for this crash type, which makes me think that maybe the telemetry session id just isn't available inside the content process?
https://searchfox.org/mozilla-central/rev/8848b9741fc4ee4e9bc3ae83ea0fc048da39979f/toolkit/crashreporter/CrashAnnotations.yaml#698
:gsvelto, do you know the answer to :tdsmith's question?
Flags: needinfo?(wlachance) → needinfo?(gsvelto)
Assignee | ||
Comment 2•6 years ago
|
||
I had a quick look and we do put the session ID in every crash ping:
https://searchfox.org/mozilla-central/rev/fc3d974254660b34638b2af9d5431618b191b233/toolkit/components/crashes/CrashManager.jsm#663
However, if it's not among the crash annotations in the first place it won't be added to it. For main process crashes we add it manually within the exception handler:
https://searchfox.org/mozilla-central/rev/fc3d974254660b34638b2af9d5431618b191b233/toolkit/crashreporter/nsExceptionHandler.cpp#1079
My guess is that we don't do it for content crashes. I'll have a look at what's needed to add it. Fortunately it doesn't matter if it's not accessible in the content process because the ping will be sent from the main process which has access to it.
Flags: needinfo?(gsvelto)
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → gsvelto
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•6 years ago
|
||
Reporter | ||
Comment 4•6 years ago
|
||
Awesome! Thanks for looking into this. Could we do this for GPU process crashes as well?
Assignee | ||
Comment 5•6 years ago
|
||
(In reply to Tim Smith 👨🔬 [:tdsmith] from comment #4)
> Awesome! Thanks for looking into this. Could we do this for GPU process
> crashes as well?
I haven't yet seen how GPU process crashes are handled, I'll have a look tomorrow. Chances are this change is sufficient for them too.
Assignee | ||
Comment 6•6 years ago
|
||
I just tested this on Windows and I can confirm that this patch also adds the telemetry session ID entry for GPU process crashes.
Pushed by gsvelto@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/41cbf7beff10
Add the telemetry session ID to content crash pings r=ted
Comment 8•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox65:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in
before you can comment on or make changes to this bug.
Description
•