Closed
Bug 1578422
Opened 6 years ago
Closed 6 years ago
Failure to setup shared memory in the CrashReporterClient should crash on Nightly to catch problems
Categories
(Toolkit :: Crash Reporting, enhancement, P1)
Toolkit
Crash Reporting
Tracking
()
RESOLVED
FIXED
mozilla71
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: bobowen, Assigned: bobowen)
References
Details
Attachments
(1 file)
Currently, if the creation and sharing of shared memory (for crash annotations) fails in CrashReporterClient::InitSingleton, it is silently ignored.
We should make this crash in Nightly (and DevEdition), so that we don't silently lose annotations.
It makes sense to ignore it for Beta and Release.
| Assignee | ||
Comment 1•6 years ago
|
||
jld: just so it doesn't come as a surprise, I'm just intending to land your patch here, with the commit comment updated.
Comment 2•6 years ago
|
||
Commit message looks good to me; thanks for taking care of this.
| Assignee | ||
Comment 3•6 years ago
|
||
This will help to catch changes that cause a loss of annotations without
affecting Release or Beta.
This also makes CrashReporterClient::InitSingleton return void as the previous
bool was ignored in all cases.
Pushed by bobowencode@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/a8a222c75f5c
MOZ_DIAGNOSTIC_ASSERT when shared memory setup fails in CrashReporterClient::InitSingleton. r=gsvelto
Comment 5•6 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in
before you can comment on or make changes to this bug.
Description
•