Crash in audiounit_property_listener_callback
Categories
(Core :: Audio/Video: cubeb, defect, P3)
Tracking
()
People
(Reporter: abr, Unassigned)
References
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is report bp-c0764ea6-1e33-4c0f-884b-936b42160830. ============================================================= Potentially relevant actions leading to this crash: - I had run a WebRTC call (using appear.in) some while ago - Shortly after the call, I unplugged my headphones - Some time later (~30 minutes), I plugged my headphones back in. Within 10 seconds, Firefox crashed. I'm putting this in cubeb, since that's the source file indicated when the crash happens -- although it may be a webrtc issue.
Comment 1•8 years ago
|
||
See the signature; ongoing crash issue at low frequency
Comment 2•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Comment 3•3 years ago
|
||
Hi Adam, we tried to reproduce this issue on our end with our latest Firefox builds but no issues occur on appear.in as for the crash signature it seems that the crash reports can't be found anymore, does this issue still occur on your end ?
Can you please try with our latest builds ? our latest release can be found here: https://www.mozilla.org/en-US/firefox/new/
Reporter | ||
Comment 4•3 years ago
|
||
(In reply to Rares Doghi from comment #3)
Hi Adam, we tried to reproduce this issue on our end with our latest Firefox builds but no issues occur on appear.in as for the crash signature it seems that the crash reports can't be found anymore, does this issue still occur on your end ?
Can you please try with our latest builds ? our latest release can be found here: https://www.mozilla.org/en-US/firefox/new/
There are no hard steps to reproduce, as this crash is very sporadic. However, based on crash-stats, all of the crash reports for the past 6 months have been under OS X in an ESR 60 build. Given that ESR 60 has been out of support since 2019, it's probably safe to consider this issue resolved.
Comment 5•3 years ago
|
||
I will close this issue with Works for me for now but if the crash reports are starting to reoccur we can definitely reopen this issue. Thank you for the info.
Description
•