[dev] BUG: ratox 100% CPU after other party dropped call
Hi,
Here is bug report. ratox is handling the incoming call and calling
party stops it:
1. call utox -> ratox
2. ( sleep 1; sox ../example.wav -r 48000 -c 1 -e signed -b 16 -t
raw -; sleep 2 ) < call_out > call_in
3. while utox hears example.wav (has to be long enough), stop the call
in utox
Existing outcome:
- ratox is in 99% and effectively goes offline in several seconds
- sox is still running untill kill -9
- after the sox murder ratox resumes normal operation and returns online
Expected outcome:
- ratox should drop call and close the pipes (for sox to exit too).
Does this makes sense?
Regards,
Myroslav
Received on Tue Oct 14 2014 - 17:37:35 CEST
This archive was generated by hypermail 2.3.0
: Tue Oct 14 2014 - 17:48:07 CEST