After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 549342 - Pipeline freezes rarely when I play it
Pipeline freezes rarely when I play it
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-python
0.10.18
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-25 18:52 UTC by Roberto Faga
Modified: 2010-12-30 00:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Roberto Faga 2008-08-25 18:52:55 UTC
I put a code at pastebin that do this bug [1], but it's very rarely. In my application [2] it freezes more times. If I put a time.sleep of 1 sec between the pipeline construction and change state, it works every time. I already checked if the connections are connected, the only thing that happens when it freezes is, the state never goes to PLAYING state, it stops at READY state and gives me the total time, and no error message.

[1] - http://gstreamer.pastebin.com/m4fd1d90e
[2] - http://gstreamer.freedesktop.org/wiki/MediaServices
Comment 1 Roberto Faga 2008-08-27 15:13:49 UTC
Stefan corrected the code to exit rightly , so check http://gstreamer.pastebin.com/m1a944946 for the updated code. Also, it could be necessary to try many times to bug.
Comment 2 Tim-Philipp Müller 2010-12-29 23:43:22 UTC
The pastebins seem to have expired.

Also, does it work with gst-launch? What makes you think this is a bug in GStreamer and/or gst-python and not your code?
Comment 3 Roberto Faga 2010-12-29 23:59:04 UTC
Ah, sorry, I forgot to close this bug many time ago. I remember it stopped with a gstreamer update, probably on the end of 2008, so I'll mark it as resolved.
Comment 4 Tim-Philipp Müller 2010-12-30 00:05:07 UTC
Great, thanks for the fast follow-up. I'll change it to OBSOLETE then since we don't know what exactly fixed it.