On Wed, 2012-04-04 at 09:34 +0300, Tanu Kaskinen wrote: > Checking whether the input is unlinked in process_msg should get rid of > this problem. But so should your suggestion of changing the process_msg > function to pa_sink_input_process_msg. Which fix would be better? (I > would prefer my fix, but that may be only due to bias.) Does somebody know what happens to the code of a dynamically loaded module when a module gets unloaded? Does it get freed? If so, sink_input_process_msg_cb will point to freed memory, and resetting the callback is obviously the right choice. -- Tanu
