GNOME Bugzilla – Bug 587674
[playbin2] pipeline gets stuck when stopping an ogg webradio stream
Last modified: 2010-04-15 07:00:52 UTC
Please describe the problem: when playing a webradio stream in ogg format, after a short time, audioconvert keeps spamming an info line and when i try stopping the pipeline after this point, i get locked in a state transition and the pipeline never reaches NULL. Steps to reproduce: 1. GST_DEBUG=*:3 gst-launch playbin2 uri=http://streaming.tidenet.de:8000/tide128.ogg > oggstream_stop_lock.log 2>&1 1b) let it play for about 2 minutes and then CTRL-C out 2. GST_DEBUG=*:3 gst-launch playbin2 uri=http://streaming.tidenet.de:8000/tide128.ogg > oggstream_stop_nolock.log 2>&1 2b) CTRL-C out right after it's done prebuffering and started playing Actual results: 1. the described problem occurs: pipelines doesn't stop and gst-launch doesn't quit. (in case of our application enigma2, it locks there of course) 2. stops and quits as expected Expected results: stop correctly also after having played for a while Does this happen every time? it's reproduceably as described Other information: logs to be uploaded
Created attachment 137777 [details] GST_DEBUG=*:3 gst-launch playbin2 uri=http://streaming.tidenet.de:8000/tide128.ogg > oggstream_stop_nolock.log 2>&1 not a higher debug level because otherwise it's too cpu-consuming to decode the audio
Created attachment 137780 [details] GST_DEBUG=*:3 gst-launch playbin2 uri=http://streaming.tidenet.de:8000/tide128.ogg > oggstream_stop_lock.log 2>&1
concerning reproducibility: i've had it playing for 5 minutes+ two times without the audioconvert info coming up, so it may depend on the song/file actually emitted by the webradio server (?) also it should be mentioned, that we use the integer-version of audioconvert
Couldn't reproduce this so far. If there's a dead lock or it "gets stuck", a 'thread apply all bt' gdb stack trace would be the most useful.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
okay cool, i had forgotten about this issue but i've tried it with that very stream again under the current release 0.10.28 et voilà it works