GNOME Bugzilla – Bug 397654
gstasfdemux.c:493: assertion failed: (*p_size >= 2)
Last modified: 2007-03-24 19:26:20 UTC
Version: 2.16.4 What were you doing when the application crashed? I tried to fast forward in Totem when it crashed Distribution: Gentoo Base System version 1.12.8 Gnome Release: 2.16.2 2006-12-05 (Gentoo) BugBuddy Version: 2.16.0 Memory status: size: 238104576 vsize: 0 resident: 238104576 share: 0 rss: 54038528 rss_rlim: 0 CPU usage: start_time: 1169046795 rtime: 0 utime: 216 stime: 0 cutime:198 cstime: 0 timeout: 18 it_real_value: 0 frequency: 5 Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223309632 (LWP 10380)] [New Thread -1376973936 (LWP 10393)] [New Thread -1367110768 (LWP 10392)] [New Thread -1358636144 (LWP 10391)] [New Thread -1341387888 (LWP 10389)] [New Thread -1332995184 (LWP 10388)] [New Thread -1321378928 (LWP 10387)] [New Thread -1306883184 (LWP 10386)] [New Thread -1297716336 (LWP 10385)] 0xb7f5b410 in __kernel_vsyscall ()
+ Trace 102984
I should note that I tried to FF by pulling the slider. I opened the movie from within Opera by double-clicking it, thereby launching Totem.
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://www.gnome.org/projects/totem/#bugs for more information on how to do so. Thanks in advance!
I don't think this will be of much additional help, but I started totem with "--debug" and got this: ** ERROR **: file gstasfdemux.c: line 493 (gst_asf_demux_get_var_length): assertion failed: (*p_size >= 2) aborting... The backtrace from gdb was not helpful, even though I compiled with the debug use-flag on gentoo, as it seems that the symbols need to come from elsewhere, as most of the stack trace is useless.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 336370 ***