GNOME Bugzilla – Bug 412870
[ximage] g_assert() in gst_ximagesink_setcaps() triggered
Last modified: 2008-11-15 17:17:36 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: 152178688 vsize: 0 resident: 152178688 share: 0 rss: 46772224 rss_rlim: 0 CPU usage: start_time: 1172623784 rtime: 0 utime: 3740 stime: 0 cutime:3543 cstime: 0 timeout: 197 it_real_value: 0 frequency: 5 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 -1226144080 (LWP 6850)] [New Thread -1325692000 (LWP 7077)] [New Thread -1360008288 (LWP 7076)] [New Thread -1308709984 (LWP 7073)] [New Thread -1335010400 (LWP 7056)] [New Thread -1246336096 (LWP 7043)] [New Thread -1317102688 (LWP 7026)] [New Thread -1300223072 (LWP 6872)] [New Thread -1282974816 (LWP 6870)] [New Thread -1274442848 (LWP 6869)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 114492
Thread 6 (Thread -1246336096 (LWP 7043))
Bug reporter: can you reproduce this issue, or did it only happen once? It seems like it aborts in line 1326 in ximagesink: 1315 : GST_VIDEO_SINK_WIDTH (ximagesink) = new_width; 1316 : GST_VIDEO_SINK_HEIGHT (ximagesink) = new_height; ... .... 1326 : g_assert (GST_VIDEO_SINK_WIDTH (ximagesink) > 0); 1327 : g_assert (GST_VIDEO_SINK_HEIGHT (ximagesink) > 0); but both new_width/new_height seem to be reasonable values (and should be given the allowed caps). I don't see right now how this can happen. The only other place where GST_VIDEO_SINK_WIDTH is set (to 0) is in the state change function for PAUSED=>READY, but when that is called the pad should already be flushing and streaming be stopped as far as I know. No idea what's going on here.
Race condition with ximagesink state_change, so probably either a core issue or xvimagesink issue => moving to GStreamer. Issue might be fixed already.
*** Bug 418804 has been marked as a duplicate of this bug. ***
Might be related to bug #420106
> Bug reporter: can you reproduce this issue, or did it only happen once? Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!