On 03/27/2012 11:54 AM, Dalleau, Frederic wrote: > Hi, > >> >> No, I just saw the crash report on launchpad and tried to figure out the >> likely cause for it. The person in question had combined module-null-sink >> with module-loopback and got a segfault from sink_input_update_max_request >> calling adjust_rates with a null u->source. >> >> For reference, the stack trace is here: >> >> https://bugs.launchpad.net/bugs/946400 >> > > Can someone get in touch with bug committer? > That would be helpful to know if either patch fixes his issue. Ok, I've now sent a message to him using Launchpad's contact service, and I'm waiting for hist reply. -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic
