I've noticed that modules unload in the same order that they are
created: i e, if module A loads first, and then module B, then module A
is also unloaded before module B when pulseaudio is shutting down.
It feels more logical to me to have it the other way around, like a
"module stack", so if module A is loaded first, it should be unloaded last.
Now, if you agree with me, dare we switch this around? It would at least
lead to that there is no module-null-sink loaded at shutdown ( \o/ ),
and maybe unloading module-dbus-protocol before module-udev-detect would
also reduce the risk of SIGSEGVs discovered yesterday.
But there might be things I'm not seeing, so what do you think?
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
_______________________________________________
pulseaudio-discuss mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
