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. Regards, Fr?d?ric
