1631794 - Crash in [@ audiocapturerhk64.dll | `anonymous namespace'::refill_callback_output] from Audials One

Status: RESOLVED WORKSFORME

(External Software Affecting Firefox :: Other, defect)

Description

[[:philipp]]

This bug is for crash report bp-bf2a55a8-337e-4599-be30-7140d0200418.

Top 10 frames of crashing thread:

0 audiocapturerhk64.dll audiocapturerhk64.dll@0x1db52 
1 audiocapturerhk64.dll audiocapturerhk64.dll@0x1de7b 
2 audiocapturerhk64.dll audiocapturerhk64.dll@0x1d8a8 
3 audiocapturerhk64.dll audiocapturerhk64.dll@0x1fafa 
4 audiocapturerhk64.dll audiocapturerhk64.dll@0x205df 
5 xul.dll `anonymous namespace'::refill_callback_output media/libcubeb/src/cubeb_wasapi.cpp:1112
6 xul.dll `anonymous namespace'::wasapi_stream_render_loop media/libcubeb/src/cubeb_wasapi.cpp
7 ucrtbase.dll thread_start<unsigned int > 
8 kernel32.dll BaseThreadInitThunk 
9 ntdll.dll RtlUserThreadStart 

these content crashes during media playback started rising 5 days ago. audiocapturerhk64.dll/audiocapturerhk32.dll seems to be part of external software product "Audials One" (https://audials.com/en/one/functions.html).
going through a couple of reports, the version of the crashing module is always '3.3.133.0', so perhaps they pushed a recent update introducing these issues around the mentioned timeframe.

Comment 1

[Nils Ohlmeier [:drno]]

Alex, do you think this could be related to any recent cubeb update we did?

Comment 2

[Alex Chronopoulos [:achronop]]

The crash is happening in third party software and not firefox. This software looks like a "fake audio driver" used to redirect the audio buffers between applications similar to soundflower in OSX. Paul knew about it and provided good information. The crash looks like an unhandled exception on their side. I have contacted them by the general contact form found on their page. I will update the bug as soon as I have any news.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:gcp, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 4

[Gian-Carlo Pascutto [:gcp]]

Hi Alex, did you get any replies? It looks like the crashes stopped as abruptly as they started, did they push out a fix?

Comment 5

[Alex Chronopoulos [:achronop]]

No, I haven't heard back from them. Nice that the crashes have stopped, they may have fixed the error regardless. In any case, IMO it is not worth keeping this bug open there is nothing we can do our end.