GNOME Bugzilla – Bug 577236
missing initialization in xvimagesink
Last modified: 2009-03-30 12:10:47 UTC
A missing initialization can cause g_thread_join to be called with some random argument, leading to an abort() in glib. --- sys/xvimage/xvimagesink.c.orig 2009-01-13 23:17:00.000000000 +0100 +++ sys/xvimage/xvimagesink.c @@ -3211,6 +3211,7 @@ gst_xvimagesink_init (GstXvImageSink * x xvimagesink->synchronous = FALSE; xvimagesink->double_buffer = TRUE; + xvimagesink->event_thread = NULL; xvimagesink->running = FALSE; xvimagesink->keep_aspect = FALSE; xvimagesink->handle_events = TRUE;
If you're seeing an abort, this isn't the cause - gobject initialises object structures to 0 at allocation, so this extra statement will have no effect.
It seems you are right... There seems to be some rather subtle memory corruption. I've only seen the crash with totem and its coherence/twisted UPnP plugin. I'll close the bug.