Sound resource persisting post-quit for looped sounds - ALSA

I installed a virtual spa-bath in my under-swamp bunker recently which includes a sloshing water sound loop.

I just turned on my speakers to listen to some music this morning and the water is still sloshing away 12 hours after I quit the SL session (I left the PC running overnight on some data processing tasks).

This is very likely the cause of some of the resource-already-in-use crashing-on-login behaviour that is quite common these past few months.

I am passing my sound via the ULCER ^H^H^H^H^H ALSA sound system ATM.


(actually, I stopped calling it ULCER when it was integrated into the kernel tree and stopped being a pain to compile in

browsing my process list, I found:

Secondlife
Do not directly

were still running. Though with no measurable cpu usage.

Killed them and the sound stopped.

My last SL session quit seemed to terminate properly via the Quit menu option (ie, I didn't have to X-kill the SL window).

This would explain why sessions that I restart after an apparently correct quit run at 1/3 the fps of sessions I have to forcibly kill - the old quit-out-of session is hanging about locking up resources!

yay