Crash in [@ cubeb_coreaudio::backend::device_property::get_device_streams]
Categories
(Core :: Audio/Video: cubeb, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox127 | --- | unaffected |
firefox128 | + | fixed |
firefox129 | + | fixed |
People
(Reporter: release-mgmt-account-bot, Assigned: pehrsons)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: crash, regression)
Crash Data
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
Crash report: https://crash-stats.mozilla.org/report/index/7f8fae61-15b1-4dfa-9252-8ade80240610
MOZ_CRASH Reason: assertion `left != right` failed left: 0 right: 0
Top 10 frames of crashing thread:
0 XUL MOZ_Crash mfbt/Assertions.h:317
0 XUL RustMozCrash mozglue/static/rust/wrappers.cpp:18
1 XUL mozglue_static::panic_hook mozglue/static/rust/lib.rs:98
2 XUL core::ops::function::Fn::call library/core/src/ops/function.rs:79
3 XUL <alloc::boxed::Box<F, A> as core::ops::function::Fn<Args>>::call library/alloc/src/boxed.rs:2034
3 XUL std::panicking::rust_panic_with_hook library/std/src/panicking.rs:783
4 XUL std::panicking::begin_panic_handler::{{closure}} library/std/src/panicking.rs:657
5 XUL std::sys_common::backtrace::__rust_end_short_backtrace library/std/src/sys_common/backtrace.rs:171
6 XUL rust_begin_unwind library/std/src/panicking.rs:645
7 XUL core::panicking::panic_fmt library/core/src/panicking.rs:72
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2024-06-10
- Process type: Parent
- Is startup crash: No
- Has user comments: No
- Is null crash: Yes - all crashes happened on null or near null memory address
By analyzing the backtrace, the regression may have been introduced by a patch [1] to fix Bug 1890186.
[1] https://hg.mozilla.org/mozilla-central/rev?node=ad954710c53f
:pehrsons, since you are the author of the potential regressor, could you please take a look?
Assignee | ||
Comment 1•4 months ago
|
||
[Tracking Requested - why for this release]: Looks like a bad assumption that aggregate devices cannot have an unknown sub device. Unclear when this can happen but it brings down the main process if it does.
Assignee | ||
Comment 2•4 months ago
|
||
Updated•4 months ago
|
Comment 4•4 months ago
|
||
bugherder |
Assignee | ||
Comment 5•4 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D213930
Updated•4 months ago
|
Comment 6•4 months ago
|
||
beta Uplift Approval Request
- User impact if declined: Main process may crash when enumerating input devices. Exact condition unclear.
- Code covered by automated testing: no
- Fix verified in Nightly: no
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: N/A
- Risk associated with taking this patch: Very low
- Explanation of risk level: This is just a guard preventing a call from happening with a certain, invalid, value.
- String changes made/needed: None
- Is Android affected?: no
Updated•4 months ago
|
Updated•4 months ago
|
Description
•