GNOME Bugzilla – Bug 570716
Crash in gst_ring_buffer_commit_full
Last modified: 2010-05-10 10:13:58 UTC
Version: 2.22.2 What were you doing when the application crashed? Just opened a video Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 575713280 vsize: 575713280 resident: 50618368 share: 16941056 rss: 50618368 rss_rlim: 18446744073709551615 CPU usage: start_time: 1233871371 rtime: 62 utime: 54 stime: 8 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' [Thread debugging using libthread_db enabled] [New Thread 0x7f56aed61700 (LWP 28254)] [New Thread 0x442b4950 (LWP 28263)] [New Thread 0x43ab3950 (LWP 28262)] [New Thread 0x432b2950 (LWP 28261)] [New Thread 0x42ab1950 (LWP 28259)] [New Thread 0x416ab950 (LWP 28258)] [New Thread 0x422b0950 (LWP 28257)] [New Thread 0x40eaa950 (LWP 28256)] 0x00007f56a8214b66 in poll () from /lib/libc.so.6
+ Trace 212281
Thread 4 (Thread 0x432b2950 (LWP 28261))
----------- .xsession-errors (409442 sec old) --------------------- (evolution:10954): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:10954): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:10954): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:10954): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:10954): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution:10954): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed (evolution: ...Too much output, ignoring rest... --------------------------------------------------
Looks like an OOM condition or a problem in GStreamer.
0.10.19 is quite old. Could you retry with the version in sid please?
To be honest i've not seen it ever crash again since that one happened. :)
Let's close this as obsolete then :)