Closed
Bug 1610263
Opened 4 years ago
Closed 4 months ago
Crash in [@ <name omitted> | mozilla::AudioCallbackDriver::~AudioCallbackDriver]
Categories
(Core :: Audio/Video: MediaStreamGraph, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gsvelto, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-d90f2980-2ae6-4393-8772-bfc1e0200120.
Top 10 frames of crashing thread:
0 libmozglue.dylib <name omitted> mozglue/misc/Mutex_posix.cpp:119
1 XUL mozilla::AudioCallbackDriver::~AudioCallbackDriver dom/media/GraphDriver.cpp:536
2 XUL mozilla::AudioCallbackDriver::~AudioCallbackDriver dom/media/GraphDriver.cpp:521
3 XUL mozilla::AudioCallbackDriver::Release dom/media/GraphDriver.h:559
4 XUL mozilla::detail::RunnableFunction<mozilla::AudioCallbackDriver::DeviceChangedCallback xpcom/threads/nsThreadUtils.h:554
5 XUL mozilla::Runnable::Release xpcom/threads/nsThreadUtils.cpp:54
6 XUL nsThreadPool::Run xpcom/threads/nsThreadPool.cpp:301
7 XUL non-virtual thunk to nsThreadPool::Run xpcom/threads/nsThreadPool.cpp
8 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1220
9 XUL <name omitted> xpcom/threads/nsThreadUtils.cpp:486
The raw crash reason is:
MOZ_CRASH(mozilla::detail::MutexImpl::~MutexImpl: pthread_mutex_destroy failed)
This doesn't look like a new crash, just very low-volume.
Component: Audio/Video → Audio/Video: MediaStreamGraph
Updated•4 years ago
|
Priority: -- → P2
Comment 1•4 years ago
|
||
All the crashes are made with the rust audiounit backend which became available by default with Bug 1606690, 5 days ago. Probably it has happened to those activated the flag manually early before that day. Thankfully, we don't have any crash since Bug 1606690 landed which let me hope that it has been fixed in the meantime. Let's monitor for a few more days for new occurrences.
Updated•4 years ago
|
Severity: normal → S3
Comment 2•4 months ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•