Okay i cannot reproduce this but I have heard about this issue since Lucid. Whereby when indicator-sound-service attempt to connect the pulse daemon and for whatever reason the daemon is not running but it should be, the respawn behaviour of pulse goes into overdrive and cripples a CPU. I am going to assign this also to pulse because indicator-sound does not do anything unorthodox there.
Okay i cannot reproduce this but I have heard about this issue since Lucid. Whereby when indicator- sound-service attempt to connect the pulse daemon and for whatever reason the daemon is not running but it should be, the respawn behaviour of pulse goes into overdrive and cripples a CPU. I am going to assign this also to pulse because indicator-sound does not do anything unorthodox there.