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 512563 - gst/gstbin unit test deadlock in test_children_state_change_order_semi_sink.
gst/gstbin unit test deadlock in test_children_state_change_order_semi_sink.
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal major
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-28 14:01 UTC by Sebastian Dröge (slomo)
Modified: 2008-04-23 13:23 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gstbin-deadlock.log.bz2 (3.85 KB, application/octet-stream)
2008-01-28 14:05 UTC, Sebastian Dröge (slomo) 		Details

Description Sebastian Dröge (slomo) 2008-01-28 14:01:19 UTC 
Hi,
with latest core CVS the GstBin unit test deadlocks in test_children_state_change_order_semi_sink.

The deadlock happens at line 710:
ret = gst_element_set_state (pipeline, GST_STATE_READY);

attached is a log with GST_DEBUG=3, every higher dbug level made it impossible to reproduce but it always happens with 3 and lower levels.
Comment 1 Sebastian Dröge (slomo) 2008-01-28 14:05:59 UTC 
Created attachment 103879 [details]
gstbin-deadlock.log.bz2
Comment 2 Jan Schmidt 2008-01-28 14:52:24 UTC 
I can't reproduce it locally, using the pre-release core. Do you have any local changes?
Comment 3 Sebastian Dröge (slomo) 2008-01-28 14:55:53 UTC 
Not and that machine... the machine is rather slow so maybe that's the problem.
Comment 4 Wim Taymans 2008-03-03 15:31:56 UTC 
can you make a stacktrace when it hangs?
Comment 5 Sebastian Dröge (slomo) 2008-04-23 13:23:57 UTC 
This bug has fixed itself after updating the system, including a new version of check.