[pulseaudio-tickets] [PulseAudio] #195: possible deadlocks when running pulseaudio with --high-priority=1

PulseAudio trac-noreply at tango.0pointer.de
Fri Dec 21 03:34:25 PST 2007


#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 
 Keywords:  SCHED_FIFO   |  
-------------------------+--------------------------------------------------
 Originally reported to pulse-audio discuss:
 https://tango.0pointer.de/pipermail/pulseaudio-
 discuss/2007-December/001001.html

 {{{
 --cut--
 This is probably a known issue, but I'm constantly hitting
 a deadlock when running Pulseaudio (0.9.7) with SCHED_FIFO
 (--high-priority=1).

 I can reproduce it as follows:

 - run pulseaudio (self-compiled, debian stable) with --high-priority=1
 - first client: while [ 1 ] ; do aplay -D pulse foo.wav ; done
 - second: while [ 1 ] ; do aplay -D pulse foo.wav ; done

 At some point, pulseaudio gets stuck and backtrace shows its
 stuck in memblock.c:pa_memblock_unref() -> memblock_free()
 -> pa_mutex_lock().
 At some point, pulseaudio gets stuck and backtrace shows its
 stuck in memblock.c:pa_memblock_unref() -> memblock_free()
 -> pa_mutex_lock().
 --cut--
 }}}

-- 
Ticket URL: <http://www.pulseaudio.org/ticket/195>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server


More information about the pulseaudio-bugs mailing list