GNOME Bugzilla – Bug 620023
Crash in __GI___libc_free, camel_exception_set at camel-exception.c line 139
Last modified: 2011-11-08 11:27:56 UTC
What were you doing when the application crashed? Changed the backend from IMAP to IMAP+. Then I was enabling threading and changing order. When I changed the folder, the application crashed. Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-amd64 #1 SMP Mon May 17 17:51:57 UTC 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 991117312 vsize: 991117312 resident: 131887104 share: 30699520 rss: 131887104 rss_rlim: 18446744073709551615 CPU usage: start_time: 1275067109 rtime: 29789 utime: 26989 stime: 2800 cutime:15 cstime: 53 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f52fb1ec910 (LWP 24480)] [New Thread 0x7f52d975b910 (LWP 23900)] [New Thread 0x7f52d9f5c910 (LWP 22876)] [New Thread 0x7f52da75d910 (LWP 22875)] [New Thread 0x7f52dcb80910 (LWP 22868)] [New Thread 0x7f52ddb82910 (LWP 22600)] [New Thread 0x7f52dd381910 (LWP 22599)] [New Thread 0x7f52dbb7e910 (LWP 22574)] [New Thread 0x7f52de383910 (LWP 22565)] [New Thread 0x7f52eccf0910 (LWP 22564)] [New Thread 0x7f52e5364910 (LWP 22561)] [New Thread 0x7f52ee91c910 (LWP 6792)] [New Thread 0x7f52fa9e7910 (LWP 6791)] [New Thread 0x7f52fc1ea910 (LWP 6782)] [New Thread 0x7f52fc9eb910 (LWP 6781)] [New Thread 0x7f52fd415910 (LWP 6780)] [New Thread 0x7f52fdc16910 (LWP 6779)] 0x00007f530bc6f5fd in __libc_waitpid (pid=24488, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 222153
Thread 9 (Thread 0x7f52dbb7e910 (LWP 22574))
Inferior 1 [process 6777] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** camel **: camel_data_wrapper_set_mime_type_field: assertion `mime_type != NULL' failed ----------- .xsession-errors --------------------- ** (eog:18845): WARNING **: Message did not receive a reply (timeout by message bus) Error: May not be a PDF file (continuing anyway) (evolution:6777): camel-WARNING **: Could not open converter for '_iso-2022-jp$ESC' to 'UTF-8' charset (evolution:6777): camel-WARNING **: Could not open converter for '3D' to 'UTF-8' charset e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: Keine passenden Ergebnisse) e-data-server-ui-Message: Die Schlüsselwertedatei enthält nicht die Gruppe »Passwords-Mail« Warnung der Fensterverwaltung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x800023 (Kennwort) Warnung der Fensterverwaltung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address (wrong library or version mismatch?) 41 ../sysdeps/unix/sysv/linux/waitpid.c: Datei oder Verzeichnis nicht gefunden. --------------------------------------------------
I'm not sure but it looks like this is related to the IMAP+ backend. There I observed this several times during the last minutes. It either freezes (pretty reproducible by trying to read messages after changing ordering or threading in a folder) or it crashes (simply changing from one folder to another for several times). I know this is not a way to reproduce the bug. But maybe you can observe the same. The IMAP sever is dovecot.
I'm seeing a similar crash, with a significantly matching backtrace.
+ Trace 222378
The crash occured while switching directoris. The IMAP server is Courier.
hopefully fixed in bug 632532 Can you please check again whether this issue still happens in Evolution 2.32.2 or 3.0 and update this report by adding a comment and changing the "Version" field? Thanks a lot.
I've still been seeing IMAPX crashes in 2.32.2 when changing the folder. I haven't bothered to take a stack trace recently, so I don't know if it's the same crash. It's a lot more intermittent, so I'm sure it will be more difficult to obtain a recent trace. I'll see what happens with 3.0 when Debian uploads the final 3.0 package.
any news ken?
Ken, please paste the updated trace in case you can reproduce the bug with Evolution 3.0 or if you feel that's different, please open a new bug, tia
Can you please check again whether this issue still happens in Evolution 3.0.3 or 3.2 and update this report by adding a comment and changing the "Version" field? Thanks a lot.
Please feel free to reopen this bug if the problem still occurs with a newer version of Evolution.