macOS Crash in [@ rtc::scoped_refptr<T>::operator=]
Categories
(Core :: WebRTC: Audio/Video, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox109 | --- | unaffected |
firefox110 | --- | wontfix |
firefox111 | + | fixed |
People
(Reporter: aryx, Assigned: pehrsons)
References
(Regression)
Details
(Keywords: crash, regression)
Crash Data
5 crashes for beta and nightly >= v110, all on macOS. First reported crash for 111.0a1 20230116211903 - the regressing change should have landed recently, could it be bug 1806605?
Crash report: https://crash-stats.mozilla.org/report/index/da731cea-e192-4fb6-b566-83b720230118
Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS
Top 10 frames of crashing thread:
0 ? @0x000001010cc6f1ce
1 XUL rtc::scoped_refptr<webrtc::VideoCaptureModule>::operator= third_party/libwebrtc/api/scoped_refptr.h:127
1 XUL mozilla::camera::VideoEngine::ReleaseVideoCapture const dom/media/systemservices/VideoEngine.cpp:127
1 XUL std::__1::__invoke<mozilla::camera::VideoEngine::ReleaseVideoCapture /builds/worker/fetches/MacOSX11.3.sdk/usr/include/c++/v1/type_traits:3747
1 XUL std::__1::__invoke_void_return_wrapper<void>::__call<mozilla::camera::VideoEngine::ReleaseVideoCapture /builds/worker/fetches/MacOSX11.3.sdk/usr/include/c++/v1/__functional_base:348
1 XUL std::__1::__function::__alloc_func<mozilla::camera::VideoEngine::ReleaseVideoCapture /builds/worker/fetches/MacOSX11.3.sdk/usr/include/c++/v1/functional:1553
1 XUL std::__1::__function::__func<mozilla::camera::VideoEngine::ReleaseVideoCapture /builds/worker/fetches/MacOSX11.3.sdk/usr/include/c++/v1/functional:1727
2 XUL std::__1::__function::__value_func<void const /builds/worker/fetches/MacOSX11.3.sdk/usr/include/c++/v1/functional:1880
2 XUL std::__1::function<void const /builds/worker/fetches/MacOSX11.3.sdk/usr/include/c++/v1/functional:2555
2 XUL mozilla::camera::VideoEngine::WithEntry dom/media/systemservices/VideoEngine.cpp:242
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
The bug is marked as tracked for firefox111 (nightly). However, the bug still isn't assigned.
:jimm, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
If this is indeed mac specific, I agree bug bug 1806605 is the likely regressor.
But be aware the code that landed in bug 1806605 is only enabled in nightly and early beta.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
S4 because this is only enabled in nightly and early beta.
Comment 4•2 years ago
|
||
Wontfix 110 as there is a low volume of crashes and this is gated pre-release channels.
Assignee | ||
Comment 5•2 years ago
|
||
I consider this an alternative symptom of the root cause behind bug 1811641.
Updated•2 years ago
|
Description
•