This bug was filed from the Socorro interface and is report bp-5c1f59b6-ad84-448c-aba2-1f1e70180125. ============================================================= Top 10 frames of crashing thread: 0 @0x7fff7905a220 1 XUL audiounit_enumerate_devices media/libcubeb/src/cubeb_audiounit.cpp:3188 2 XUL cubeb_enumerate_devices media/libcubeb/src/cubeb.c:580 3 XUL mozilla::AudioInputCubeb::UpdateDeviceList dom/media/webrtc/MediaEngineWebRTC.cpp:57 4 XUL mozilla::AudioInputCubeb::GetNumOfRecordingDevices dom/media/webrtc/MediaEngineWebRTC.h:192 5 XUL mozilla::MediaEngineWebRTC::EnumerateAudioDevices dom/media/webrtc/MediaEngineWebRTC.cpp:290 6 XUL mozilla::media::LambdaTask<mozilla::MediaManager::EnumerateRawDevices dom/media/MediaManager.cpp:1319 7 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1040 8 XUL NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:517 9 XUL mozilla::ipc::MessagePumpForNonMainThreads::Run ipc/glue/MessagePump.cpp:334 ============================================================= There is 1 crash (from 1 installation) in nightly 60 with buildid 20180125104809. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1432733. [1] https://hg.mozilla.org/mozilla-central/rev?node=590643620ec4

Paul we crash in the new `is_aggregate_device()`. Do you want to handle it ?

I'll patch it, thanks. However I don't know why this does not have a `friendly_name`. Maybe it's a thing on some weird devices?

PR upstream: https://github.com/kinetiknz/cubeb/pull/409

Please link this to the pull-from-upstream bug when it's filed

Fixed by Bug 1435307