I spoke too soon in regards to "no-cpu-limit = yes" fixing the issue. Its not fixed and is still occurring on my system. Its no longer receiving SIGXCPU signals, but it does still get a SIGKILL, the source of which I am still unsure of.
Daniel T Chen: How can you be sure its a bi-product of bug #345627 ? The description of that bug sounds nothing like what I am experiencing. The audio output is totally fine on my system (no crackles or pops). Perhaps you posted the wrong bug link?
Bug #366708 seems like it could be the same, thought that could just be a PulseAudio crash. In this case, its not crashing, its getting killed.
I spoke too soon in regards to "no-cpu-limit = yes" fixing the issue. Its not fixed and is still occurring on my system. Its no longer receiving SIGXCPU signals, but it does still get a SIGKILL, the source of which I am still unsure of.
Daniel T Chen: How can you be sure its a bi-product of bug #345627 ? The description of that bug sounds nothing like what I am experiencing. The audio output is totally fine on my system (no crackles or pops). Perhaps you posted the wrong bug link?
Bug #366708 seems like it could be the same, thought that could just be a PulseAudio crash. In this case, its not crashing, its getting killed.