GNOME Bugzilla – Bug 365501
[x/xvimagesink] race condition when creating first image buffer mini-object due to g_type_class_ref() not being thread-safe
Last modified: 2007-10-17 15:27:20 UTC
Version: 2.16.2 What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 209362944 vsize: 0 resident: 209362944 share: 0 rss: 83988480 rss_rlim: 0 CPU usage: start_time: 1161906680 rtime: 0 utime: 312 stime: 0 cutime:282 cstime: 0 timeout: 30 it_real_value: 0 frequency: 6 Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226126624 (LWP 3781)] [New Thread -1368089696 (LWP 3803)] [New Thread -1329497184 (LWP 3801)] [New Thread -1321010272 (LWP 3800)] [New Thread -1312134240 (LWP 3799)] [New Thread -1303602272 (LWP 3798)] [New Thread -1275966560 (LWP 3797)] [New Thread -1284404320 (LWP 3790)] [New Thread -1267496032 (LWP 3787)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 78613
Thread 3 (Thread -1329497184 (LWP 3801))
Gah, I thought this was fixed ages ago. Looks like g_type_class_ref() isn't entirely thread-safe either if the class doesn't exist yet. Should be fixed now: 2006-10-27 Tim-Philipp Müller <tim at centricular dot net> * sys/ximage/ximagesink.c: (gst_ximagesink_get_type): * sys/xvimage/xvimagesink.c: (gst_xvimagesink_get_type): Explicitly create our custom buffer classes at a thread-safe location as well, since g_type_class_ref() doesn't seem to be entirely thread-safe either (#365501; also see #349410).
*** Bug 368205 has been marked as a duplicate of this bug. ***
*** Bug 376772 has been marked as a duplicate of this bug. ***
*** Bug 412010 has been marked as a duplicate of this bug. ***
*** Bug 418709 has been marked as a duplicate of this bug. ***
*** Bug 417244 has been marked as a duplicate of this bug. ***
*** Bug 430297 has been marked as a duplicate of this bug. ***
*** Bug 462931 has been marked as a duplicate of this bug. ***
*** Bug 460088 has been marked as a duplicate of this bug. ***