Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10928 - [pulseaudio 0.9.10-1] Crashes Randomly: Soft CPU time limit exhausted

Attached to Project: Community Packages
Opened by Manuel Faux (faux_at) - Wednesday, 16 July 2008, 07:52 GMT
Last edited by Corrado Primier (bardo) - Sunday, 20 July 2008, 22:01 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Corrado Primier (bardo)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
PulseAudio crashes every time it was started and music (e. g. via mpd or totem) was played after some time (between ~1 min and ~ 5 min). The error message is always the same: "Soft CPU time limit exhausted, terminating.". Shortly before this, the CPU usage of PulseAudio rises to nearly 100%.

Additional info:
* Using: pulseaudio: 0.9.10-1, kernel26: 2.6.25.11-1, alsa-utils, alsa-lib: 1.0.16.1
* The shortened -vvvv output of PulseAudio:
*** Starting mpd playback:
(...)
I: sink-input.c: Created input 0 "local PulseAudio Output" on alsa_output.hw_0_0 with sample spec s16le 2ch 44100Hz and channel map front-left,front-right
D: memblockq.c: memblockq requested: maxlength=132300, tlength=88200, base=4, prebuf=86436, minreq=1764
D: memblockq.c: memblockq sanitized: maxlength=132300, tlength=88200, base=4, prebuf=86436, minreq=1764
D: memblock.c: Memory block too large for pool: 17808 > 16376
D: memblock.c: Memory block too large for pool: 22440 > 16376
*** The crash (after about 1-5min of playback):
Soft CPU time limit exhausted, terminating.
I: main.c: Daemon shutdown initiated.
(PulseAudio shuts down...)
* PulseAudio says this might be an ALSA issue: http://www.pulseaudio.org/ticket/207 , but I have the newest kernel available through pacman. I also use PulseAudio on an Fedora 9 installation (Kernel 2.6.25.10, currently) and also on an Gentoo installation (Kernel older than my Arch Linux kernel) and never had this problem.
* Maybe also related to: https://bugs.launchpad.net/bugs/221038
This task depends upon

Closed by  Corrado Primier (bardo)
Sunday, 20 July 2008, 22:01 GMT
Reason for closing:  Upstream
Comment by Corrado Primier (bardo) - Wednesday, 16 July 2008, 11:06 GMT
Yeah, I can confirm the problem when I set default-sample-channels in /etc/pulse/daemon.conf. However, when that value is left alone everything works fine on my machine. I am curious about your setup, because in your report I see:
'I: sink-input.c: Created input 0 "local PulseAudio Output" on alsa_output.hw_0_0 with sample spec s16le 2ch 44100Hz and channel map front-left,front-right'
So it looks like you're using two channels, or at least that's what it's trying to use. Could you please confirm if the workaround works and post your daemon.conf?
Comment by Manuel Faux (faux_at) - Wednesday, 16 July 2008, 12:47 GMT
I didn't touch the daemon.conf at all, but I've set 6 channels via the default.conf:
load-module module-alsa-sink device="hw:0,0" fragment_size=2048 fragments=24 channels=6 rate=48000
load-module module-alsa-source device="hw:0,0" channels=2 rate=48000

Yes, I can confirm, that the problem does not occur (as far as I can say after testing it half an hour) if I change the two lines to simply:
load-module module-alsa-sink
load-module module-alsa-source

I will try to run PA without my 6 channels for a while to determine if this is the problem.

It this *IS* the problem, is this an PA or an ALSA bug? I used PA with this kind of configuration for about half a year on Gentoo Linux (the same hardware of cause) without any problems.
Comment by Manuel Faux (faux_at) - Sunday, 20 July 2008, 20:09 GMT
I've been using PA now for five days with only two channels (default value) and not one crash. This bug is definitely caused by setting the channel amount manually.
Comment by Corrado Primier (bardo) - Sunday, 20 July 2008, 22:01 GMT
I'm closing this bug then, since it's for upstream to solve and a workaround has been found and archived. Thanks for reporting.

Loading...