GNOME Bugzilla – Bug 647623
Crash in A__g_hash_table_lookup, find_message
Last modified: 2011-05-17 13:26:24 UTC
What were you doing when the application crashed? just started Evolution and then klicked on an unread email (which is located on the exchange server) Distribution: Debian 6.0.1 Gnome Release: 2.30.2 2010-11-12 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Darklooks Icon Theme: Mist GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 788066304 vsize: 788066304 resident: 65028096 share: 25681920 rss: 65028096 rss_rlim: 18446744073709551615 CPU usage: start_time: 1302674567 rtime: 320 utime: 294 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fd295668700 (LWP 2590)] [New Thread 0x7fd27ffff700 (LWP 2577)] [New Thread 0x7fd28f7fe700 (LWP 2572)] [New Thread 0x7fd286b27700 (LWP 2571)] [New Thread 0x7fd29934d700 (LWP 2570)] [New Thread 0x7fd28dffb700 (LWP 2560)] [New Thread 0x7fd28e7fc700 (LWP 2558)] [New Thread 0x7fd28ffff700 (LWP 2555)] [New Thread 0x7fd294c3e700 (LWP 2554)] [New Thread 0x7fd295e69700 (LWP 2552)] [New Thread 0x7fd29666a700 (LWP 2551)] [New Thread 0x7fd297db6700 (LWP 2550)] [New Thread 0x7fd2985b7700 (LWP 2549)] 0x00007fd2a6a6ab4d in waitpid () from /lib/libpthread.so.0
+ Trace 226707
Thread 2 (Thread 0x7fd295668700 (LWP 2590))
Inferior 1 [process 2548] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** camel-exchange-provider **: sync_deletions: assertion `mfld->ed != NULL' failed ** camel-exchange-provider **: get_camel_folder: assertion `mfld->ed != NULL' failed ----------- .xsession-errors --------------------- ** (gnome-screensaver:2489): WARNING **: Config key not handled: /desktop/gnome/lockdown/disable_command_line ** (gnome-screensaver:2489): WARNING **: Config key not handled: /desktop/gnome/lockdown/disable_printing ** (gnome-screensaver:2489): WARNING **: Config key not handled: /desktop/gnome/lockdown/disable_print_setup ** (gnome-screensaver:2489): WARNING **: Config key not handled: /desktop/gnome/lockdown/disable_save_to_disk (evolution:2548): camel-exchange-provider-WARNING **: got_folder: 7 (evolution:2548): camel-exchange-provider-WARNING **: got_new_smtp_messages: 7 (evolution:2548): camel-exchange-provider-CRITICAL **: sync_deletions: assertion `mfld->ed != NULL' failed (evolution:2548): camel-exchange-provider-CRITICAL **: get_camel_folder: assertion `mfld->ed != NULL' failed --------------------------------------------------
related to bug 635154 or bug 634291
Thanks for a bug report. Are you able to reproduce this anyhow, please? Though it might depend on actual local message cache and new changes received from the server. The below critical warnings may not happen, thus I'm afraid that evolution-exchange is accessing some already freed memory here, or something similar. > ** camel-exchange-provider **: sync_deletions: assertion `mfld->ed != NULL' > failed > ** camel-exchange-provider **: get_camel_folder: assertion `mfld->ed != NULL' > failed Running evolution under valgrind may shed some light on the issue. You can run it like this: $ G_SLICE=always-malloc valgrind evolution &>log.txt
*** Bug 647657 has been marked as a duplicate of this bug. ***
Created attachment 187959 [details] valgrind log
Thanks for the update. Below is the snippet of accessing already freed memory. As Andre mentioned in bug #647657 comment #1, this was really fixed within bug #625570 comment #6. Please ask you distribution to backport that fix or compile evolution-exchange yourself with that fix applied. I'm marking this as a duplicate of the old bug. > Invalid read of size 8 > at 0x1A200638: sync_deletions (camel-exchange-utils.c:709) > by 0x1A201A62: camel_exchange_utils_refresh_folder (camel-exchange- > utils.c:2301) > by 0x1A1F89A0: refresh_info (camel-exchange-folder.c:177) > by 0x6C578CC: camel_folder_refresh_info (camel-folder.c:352) > by 0x16D76777: mail_msg_proxy (mail-mt.c:471) > by 0xE1ED5CE: g_thread_pool_thread_proxy (gthreadpool.c:315) > by 0xE1EB783: g_thread_create_proxy (gthread.c:1893) > by 0xA4E98B9: start_thread (pthread_create.c:300) > by 0xE52F02C: clone (clone.S:112) > Address 0x2da983e0 is 0 bytes inside a block of size 112 free'd > at 0x4C240FD: free (vg_replace_malloc.c:366) > by 0x1A200F27: get_folder_contents_online (camel-exchange-utils.c:1062) > by 0x1A20180F: get_folder_contents_online_func (camel-exchange-utils.c:1109) > by 0xE1EB783: g_thread_create_proxy (gthread.c:1893) > by 0xA4E98B9: start_thread (pthread_create.c:300) > by 0xE52F02C: clone (clone.S:112) *** This bug has been marked as a duplicate of bug 625570 ***