GNOME Bugzilla – Bug 356156
crash in Evolution: closing the main window ...
Last modified: 2006-09-17 16:04:39 UTC
What were you doing when the application crashed? closing the main window in email mode Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 163479552 vsize: 0 resident: 163479552 share: 0 rss: 41566208 rss_rlim: 0 CPU usage: start_time: 1158343870 rtime: 0 utime: 1058 stime: 0 cutime:1018 cstime: 0 timeout: 40 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' (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 -1232832848 (LWP 5766)] [New Thread -1296610400 (LWP 5785)] [New Thread -1287824480 (LWP 5782)] [New Thread -1266582624 (LWP 5775)] [New Thread -1258153056 (LWP 5769)] [New Thread -1249760352 (LWP 5768)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72423
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Okay, I think this might be better -- I am using the "unstable" version because it seems better at handling large maildir-style mailboxes, with less crashing. But it still does this, and doesn't remember which messages had been marked "read" before it crashed. Thanks, Fred Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 137043968 vsize: 0 resident: 137043968 share: 0 rss: 34521088 rss_rlim: 0 CPU usage: start_time: 1158443658 rtime: 0 utime: 7576 stime: 0 cutime:5152 cstime: 0 timeout: 2424 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232058704 (LWP 5665)] [New Thread -1322263648 (LWP 5824)] [New Thread -1313870944 (LWP 5822)] [New Thread -1305478240 (LWP 5675)] [New Thread -1292031072 (LWP 5671)] [New Thread -1268663392 (LWP 5670)] [New Thread -1260233824 (LWP 5668)] [New Thread -1251841120 (LWP 5667)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72528
Thread 1 (Thread -1232058704 (LWP 5665))
Perfect stacktrace, thanks a lot! 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 330157 ***