On Fr 29 M?r 2013 08:54:16 CET, Tanu Kaskinen wrote: > I wouldn't mind having a glance at a log with maximum verbosity, with > realtime-scheduling enabled. http://mayoneso.de/pulseaudio/log_pa_rt_enabled.tar.gz > Getting killed due to excessive CPU use suggests that PulseAudio enters a > busy-loop. Another possibility is that PulseAudio does some heavy processing, > but that shouldn't be the case with the default configuration. Have you loaded > some filter modules in PulseAudio? No, PulseAudio runs with the default configuration. > If you disable realtime-scheduling, does pulseaudio consume a lot of CPU time? It uses about 2-6 % CPU load and ~1184 seconds CPU time. > I guess you don't have rtkit installed. rtkit should be able to dynamically > remove the realtime scheduling from PulseAudio in case PulseAudio doesn't > behave nicely, before PulseAudio gets killed. Of course, if there's a busy- > loop involved, there would still be excessive CPU load... rtkit is installed.
