GNOME Bugzilla – Bug 681575
[0.11] gstnetclientclock test hangs forever on Ubuntu Quantal
Last modified: 2012-08-10 08:33:44 UTC
The gstnetclientclock test hangs forever on Ubuntu Quantal. Even the timeout of the testrunner is not killing it after some time. No idea why the testrunner does not kill it after some time but the test problem seems to be a deadlock in the GMainContext used by the clock. Testrunner process: (gdb) bt
+ Trace 230649
Created attachment 220851 [details] [review] netclientclock: simplify by using g_socket_condition_timed_wait()
Comment on attachment 220851 [details] [review] netclientclock: simplify by using g_socket_condition_timed_wait() Works for me
commit fe082cbe24a4bfd7131921d820df1b7689da7b66 Author: Tim-Philipp Müller <tim@centricular.net> Date: Fri Aug 10 09:19:25 2012 +0100 netclientclock: simplify by using g_socket_condition_timed_wait() No need to use a custom main context and custom timeout sources, just use g_socket_condition_timed_wait() instead, which was added for exactly this case. Also seems to help with the unit test deadlocking with glib 2.33.x https://bugzilla.gnome.org/show_bug.cgi?id=681575