Comment 28 for bug 367671

Revision history for this message
danmb (danmbox) wrote :

From setrlimit(2): setrlimit allows the user to specify two limits -- a soft one and a hard one. For RLIMIT_RTTIME, upon exceeding the soft limit, the kernel sends a SIGXCPU every second, then a SIGKILL.

Unfortunately, pulseaudio sets the soft limit equal to the hard limit, so no warning is possible.

I'm going to change the code to make the soft limit smaller, then run pulse under gdb and get a backtrace when it receives SIGXCPU.