[pulseaudio-tickets] [PulseAudio] #195: possible deadlocks when running pulseaudio with --high-priority=1
PulseAudio
trac-noreply at tango.0pointer.de
Fri Feb 15 05:56:17 PST 2008
#195: possible deadlocks when running pulseaudio with --high-priority=1
--------------------------+-------------------------------------------------
Reporter: kaivehmanen | Owner: lennart
Type: defect | Status: new
Priority: normal | Milestone:
Component: core | Severity: normal
Resolution: | Keywords: SCHED_FIFO
--------------------------+-------------------------------------------------
Comment (by lennart):
Hmm, no this is not a known issue. So, someone else apparently has taken
the mutex of the mempool that we try to acquire. Hmm, I know this is not
easy, but could you find out which piece of code might be doing that?
What arch is this?
--
Ticket URL: <http://pulseaudio.org/ticket/195#comment:2>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server
More information about the pulseaudio-bugs
mailing list