I think we should continue here the discussion we had on "Production environment". If the backtrace you have here corresponds to the situation you described recently, that you fixed by distributing your multiple outputs accross multiple instances, then it means that when one output gets disconnected it brings liquidsoap to a deadlock, including duppy -- which is why clocks won't help. With this scenario in mind I'd suspect the on_stop callback: have you setup anything there?
Otherwise, I don't see how outputs may affect duppy. One output may freeze the whole streaming thread (which is where clocks do help) if lags instead of disconnecting quickly (we've had bugs like that in the past, not long ago). But here it's not only the main thread... We're making progress... David ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
