GNOME Bugzilla – Bug 340776
[xvimagesink] totem crash sometime when opening a video or after playing it
Last modified: 2006-12-10 19:44:36 UTC
I'm playing with totem after upgrading gst-plugins-good0.10 to 0.10.3 and it crashes often of some video when opening them or after playing them: "(totem:7854): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed (totem:7854): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed (totem:7854): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed [Thread -1277043792 (LWP 7876) exited] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1297921104 (LWP 7884)] 0xb6ae5990 in gst_xvimagesink_event_thread (xvimagesink=0x850cb68) at xvimagesink.c:934 934 while (XCheckWindowEvent (xvimagesink->xcontext->disp, (gdb) thread apply all bt
+ Trace 68044
Thread 8 (Thread -1289528400 (LWP 7877))
Thread 1 (Thread -1225476416 (LWP 7854))
Other backtrace: Program received signal SIGSEGV, Segmentation fault.
+ Trace 68045
Thread NaN (LWP 8705)
Happens with the previous version too, reassigning it
Do you have to do anything in particular to cause this or does it just happen? Also, could you do: $ G_DEBUG=fatal_warnings gdb --args totem /path/to/file to find out where exactly that warning comes from?
it looks like it happens when switching between videos or after playing one The warnings are a different issue, should I open a different bug for them? Backtrace: "GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed aborting... Program received signal SIGABRT, Aborted.
+ Trace 68049
Thread NaN (LWP 24806)
Created attachment 65390 [details] [review] patch for the warnings This patch should fix the warnings about not being able to read a GstFraction from the pixel-aspect-ratio property of the video sink in comment #4
This looks like either a totem or an xvimagesink raciness bug to me (the segfault, not the g_value_transform warning)
Committed the patch to CVS. The race still needs finding.
is this bug still present? can anyone trigger this and get a new backtrace?
Anybody still facing this?
I didn't get that issue for some time, marking as fixed