Crash in [@ cubeb_coreaudio::backend::CoreStreamData::setup]
Categories
(Core :: Audio/Video: cubeb, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox98 | --- | unaffected |
firefox99 | --- | unaffected |
firefox100 | + | fixed |
firefox101 | --- | unaffected |
People
(Reporter: aryx, Assigned: padenot)
References
(Regression)
Details
(Keywords: crash, regression)
Crash Data
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
|
Details | Review |
7 crashes from 2+ machines with macOS 12, oldest reported build ID is 100.0a1 20220326213356. Is this a regression from bug 1760774 which added the code directly executed before?
Crash report: https://crash-stats.mozilla.org/report/index/8d2394bd-c38c-430e-9f39-7fa120220331
MOZ_CRASH Reason: ```assertion failed: (left != right)
left: `0`,
right: `0````
Top 10 frames of crashing thread:
0 XUL RustMozCrash mozglue/static/rust/wrappers.cpp:18
1 XUL mozglue_static::panic_hook mozglue/static/rust/lib.rs:91
2 XUL core::ops::function::Fn::call library/core/src/ops/function.rs:70
3 XUL std::panicking::rust_panic_with_hook library/std/src/panicking.rs:610
4 XUL std::panicking::begin_panic_handler::{{closure}} library/std/src/panicking.rs:502
5 XUL std::sys_common::backtrace::__rust_end_short_backtrace library/std/src/sys_common/backtrace.rs:139
6 XUL rust_begin_unwind library/std/src/panicking.rs:498
7 XUL core::panicking::panic_fmt library/core/src/panicking.rs:116
8 XUL core::panicking::assert_failed_inner library/core/src/panicking.rs:197
9 XUL core::panicking::assert_failed library/core/src/panicking.rs:154
![]() |
||
Updated•4 months ago
|
Comment 1•4 months ago
|
||
I assume we're hitting this assert as a result of one of the get_device_transport_type
calls added to should_use_aggregate_device
in bug 1760774 (importing https://github.com/mozilla/cubeb-coreaudio-rs/pull/153) passing a self.input_device.id
or self.output_device.id
with a value of kAudioObjectUnknown
(0). Perhaps we can just remove the assert from get_device_transport_type
- it seems fine to query kAudioObjectUnknown
, it'll just fail with kAudioHardwareBadObjectError
and treat it as a non-aggregate device.
Paul, does that make sense to you?
Updated•4 months ago
|
![]() |
||
Updated•4 months ago
|
Assignee | ||
Comment 2•4 months ago
|
||
It's probably the best solution yes, thanks. I'm having a hard time figuring out what assert failed without tracing everything manually...
Assignee | ||
Updated•4 months ago
|
Updated•4 months ago
|
Comment 4•4 months ago
|
||
:padenot, can you provide a patch for beta?
![]() |
Reporter | |
Updated•4 months ago
|
Assignee | ||
Comment 5•4 months ago
|
||
Yes, likely tomorrow when it's reviewed upstream.
Assignee | ||
Comment 6•4 months ago
|
||
Anything with WASAPI is windows, unrelated to this bug, please file something else is needed I'll look into it.
Assignee | ||
Comment 7•4 months ago
|
||
Merging in 1764574, not hard to uplift I think.
Updated•4 months ago
|
Comment 8•4 months ago
|
||
Changing the priority to P1 as the bug is tracked by a release manager for the current beta.
See Triage for Bugzilla for more information.
If you disagree, please discuss with a release manager.
Assignee | ||
Comment 9•4 months ago
|
||
Assignee | ||
Comment 10•4 months ago
|
||
Comment on attachment 9272283 [details]
Bug 1762563 - Update cubeb-coreaudio-rs to 39f7e69 on beta to fix an assert crash. r?#cubeb-reviewers
Beta/Release Uplift Approval Request
- User impact if declined: Firefox crashes when an audio output device is removed.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This essentially reverts part of the code to what it currently is in release.
- String changes made/needed:
Comment 11•4 months ago
•
|
||
:padenot this hasn't landed yet, is this still something we want to get into b8?
Assignee | ||
Comment 12•4 months ago
|
||
(In reply to Dianna Smith [:diannaS] from comment #11)
:padenot this hasn't landed yet, is this still something we want to get into b8?
Certainly yes, it's not risky and fixes a crash.
Comment 13•4 months ago
|
||
Comment on attachment 9272283 [details]
Bug 1762563 - Update cubeb-coreaudio-rs to 39f7e69 on beta to fix an assert crash. r?#cubeb-reviewers
Approved fro 100.0b8
Comment 14•4 months ago
|
||
bugherderuplift |
Updated•4 months ago
|
Updated•4 months ago
|
![]() |
Reporter | |
Comment 15•4 months ago
|
||
There are also crash reports for v101 with this signature. Should those get a new bug?
Assignee | ||
Comment 16•4 months ago
|
||
(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #15)
There are also crash reports for v101 with this signature. Should those get a new bug?
Yes please.
Assignee | ||
Comment 17•4 months ago
|
||
It's only a single crash, that is different, since we landed the patches in https://bugzilla.mozilla.org/show_bug.cgi?id=1764574: https://crash-stats.mozilla.org/signature/?product=Firefox&version=101.0a1&platform=Mac%20OS%20X&build_id=%3E%3D20220414092955&signature=cubeb_coreaudio%3A%3Abackend%3A%3ACoreStreamData%3A%3Asetup&date=%3E%3D2022-03-20T00%3A00%3A00.000Z&date=%3C2022-04-20T23%3A59%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_columns=startup_crash&_sort=-date&page=1. I'll get a fix for that.
Assignee | ||
Comment 18•4 months ago
|
||
(In reply to Paul Adenot (:padenot) from comment #16)
(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #15)
There are also crash reports for v101 with this signature. Should those get a new bug?
Yes please.
I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1765969 and attached the patch there.
Description
•