[Bug 367671] [NEW] PulseAudio gets killed mysteriously

Launchpad Bug Tracker 367671 at bugs.launchpad.net
Fri Mar 5 06:30:14 UTC 2010


You have been subscribed to a public bug:

Binary package hint: pulseaudio

I'm using Ubuntu Studio 9.04 and have enabled PulseAudio
(0.9.14-0ubuntu20) with real time enabled.  While playing music I
noticed that the audio output would suddenly stop, though Amarok kept on
as if everything was fine.  I noticed that pulseaudio was no longer
running, when running it from the command line I observed again the same
behavior and the last output line from PulseAudio was "Killed".  By
attaching strace with -e trace=signal I found that it would occasionally
get a SIGXCPU signal.  On the 3rd signal, pulseaudio gets killed,
presumably by the Linux kernel.

By setting "no-cpu-limit = yes" in the /etc/pulse/daemon.conf file, it
got rid of the SIGXCPU signals, which didn't seem to be the problem,
since it is still getting a SIGKILL signal.  One additional note is that
I changed the resample-method to speex-float-1 from the default of src-
linear.  I'm not experiencing any perceptible system lockup when this
occurs, so I don't think the RT PulseAudio is taking up extended amounts
of CPU.  I'm at a loss as to where the SIGKILL is coming from.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
PulseAudio gets killed mysteriously
https://bugs.edge.launchpad.net/bugs/367671
You received this bug notification because you are a member of Kernel Bugs, which is subscribed to linux in ubuntu.




More information about the kernel-bugs mailing list