Closed
Bug 1919212
Opened 3 days ago
Closed 2 days ago
cubeb::duplex_collection_change_no_unregister gtest disables the crash reporter permanently
Categories
(Core :: Audio/Video: cubeb, defect)
Core
Audio/Video: cubeb
Tracking
()
RESOLVED
FIXED
132 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | affected |
| firefox130 | --- | wontfix |
| firefox131 | --- | wontfix |
| firefox132 | --- | fixed |
People
(Reporter: glandium, Assigned: padenot)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
mozilla::gtest::DisableCrashReporter permanently disables the crash reporter. It's meant to be used for death tests in the child process, but it's used in the parent process. That means that crashes that happen in gtests after this one are never caught by the crash reporter.
|
||
Comment 1•3 days ago
|
||
Set release status flags based on info from the regressing bug 1864143
:padenot, since you are the author of the regressor, bug 1864143, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
status-firefox130:
--- → affected
status-firefox131:
--- → affected
status-firefox132:
--- → affected
status-firefox-esr115:
--- → unaffected
status-firefox-esr128:
--- → affected
Flags: needinfo?(padenot)
|
Assignee | |
Updated•2 days ago
|
Assignee: nobody → padenot
Flags: needinfo?(padenot)
|
|
Assignee | |
Comment 2•2 days ago
|
||
Death test work by forking. We want to disable the crash reporter only in the
forked process.
Pushed by padenot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a216dc4bab0b
Only disable crash reporter in child process in test_duplex.cpp. r=pehrsons,cubeb-reviewers
|
||
Updated•2 days ago
|
Status: NEW → RESOLVED
Closed: 2 days ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•