Open Bug 996162 Opened 10 years ago Updated 2 years ago

cubeb wasapi can make DataCallbacks after stop() is called


(Core :: Audio/Video: cubeb, defect, P4)

Windows 7




(Reporter: jesup, Unassigned)



In the process of solving bugs in bug 919215, we had clear evidence (crashes and catches in VS) that we got Callbacks after stop() was called.  This may be inevitable; I'm not sure, and there were various locking issues along the way.

It's almost more of an API question: is stop() async (and since there's a STOPPED callback, it could be) or sync (in which case it makes sense to call it unlocked, and block until any callbacks resolve -- assuming no backend makes this tough to accomplish).
backlog: --- → webrtc/webaudio+
Rank: 35
Component: Audio/Video → Audio/Video: MSG/cubeb/GMP
Priority: -- → P3
backlog: webrtc/webaudio+ → ---
Component: Audio/Video: MediaStreamGraph → Audio/Video: cubeb
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4

This has been fixed in cubeb, there was/is a windows bug, but we've worked around it in cubeb.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.