GNOME Bugzilla – Bug 597297
crash in Movie Player: I was watching an xvid f...
Last modified: 2010-01-24 01:47:27 UTC
Version: 2.26.3 What were you doing when the application crashed? I was watching an xvid film, and I went to take a shower, triggering the machine to go into suspention into RAM. When waking the machine up, i saw this bug buddy. Distribution: Fedora release 11 (Leonidas) Gnome Release: 2.26.3 2009-07-07 (Red Hat, Inc) BugBuddy Version: 2.26.0 System: Linux 2.6.30.8-64.fc11.x86_64 #1 SMP Fri Sep 25 04:43:32 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10603901 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad Memory status: size: 1216655360 vsize: 1216655360 resident: 88145920 share: 48828416 rss: 88145920 rss_rlim: 18446744073709551615 CPU usage: start_time: 1254656759 rtime: 56448 utime: 49688 stime: 6760 cutime:2 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' [Thread debugging using libthread_db enabled] [New Thread 0x7f7d0dbed910 (LWP 7257)] [New Thread 0x7f7cf2e08910 (LWP 6386)] [New Thread 0x7f7cf3a41910 (LWP 6385)] [New Thread 0x7f7d05269910 (LWP 6382)] [New Thread 0x7f7d0607d910 (LWP 6381)] [New Thread 0x7f7d07df3910 (LWP 6380)] [New Thread 0x7f7d0ee3c910 (LWP 6378)] 0x000000308700ea2d in __libc_waitpid (pid=8051, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); Current language: auto; currently minimal
+ Trace 218040
Thread 1 (Thread 0x7f7d167e8800 (LWP 6376))
Current language: auto; currently minimal The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** Gdk **: The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 948 error_code 11 request_code 132 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Output of custom script "/usr/libexec/totem/totem-bugreport.py": gst-typefind-0.10 version 0.10.24 GStreamer 0.10.24 http://download.fedora.redhat.com/fedora Listened to a "video/x-msvideo" file on 2009-10-04T14:21:28 ----------- .xsession-errors (7 sec old) --------------------- warning: the debug information found in "/usr/lib/debug/usr/lib64/gstreamer-0.10/libgstvolume.so.debug" does not match "/usr/lib64/gstreamer-0.10/libgstvolume.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/gstreamer-0.10/libgstffmpegcolorspace.so.debug" does not match "/usr/lib64/gstreamer-0.10/libgstffmpegcolorspace.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib64/gstreamer-0.10/libgstffmpegcolorspace.so.debug" does not match "/usr/lib64/gstreamer-0.10/libgstffmpegcolorspace.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/gstreamer-0.10/libgstvideoscale.so.debug" does not match "/usr/lib64/gstreamer-0.10/libgstvideoscale.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib64/gstreamer-0.10/libgstvideoscale.so.debug" does not match "/usr/lib64/gstreamer-0.10/libgstvideoscale.so" (CRC mismatch). --------------------------------------------------
Is this crash reproducable? If so, could you get a debug log from Totem before it crashes, by running Totem with the following command, then uploading the generated log file here please? GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:5 totem &> totem.log
I did that, and the log file is almost 290 MiB. Do you want me to upload the whole thing (compressed of course)?
Try with GST_DEBUG=*:4 instead, but keep the level 5 log, just in case the level 4 log isn't useful enough.
I compressed it as hard as I knew how but it didn't get under the allowed size limit that GNOME's bugzilla allows. I therefore uploaded it to one of the gratis file hosting providers that are out there. Totem level 4 debug log: Link: http://www.mediafire.com/?ngmjql1yvew
What's the resolution of the video you're watching? 2046×2046? Is there any chance you could just be running out of memory?
Also, are you running Compiz, or another compositing window manager? What's your video card?
This happens for every video I have. I am running with desktop effects enabled and it is a 01:00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1) videocard using the latest proprietary driver. The film is not very large in resolution so I doubt I am running out of memory.
Could you try playing videos with desktop effects disabled please?
By disabling desktop effects, I did not have Totem crash on me. I guess that means that this bug is related to nvidia's evil proprietary driver?
You could try with the vesa driver (or nouveau, or another suitable driver), and see what happens. Regardless, the problem is somewhere in Xorg/drivers, not in Totem.
*** Bug 607898 has been marked as a duplicate of this bug. ***