Description of problem: Evolution froze. It stopped responding to anything. Then it quit all on its own. Version-Release number of selected component: evolution-3.8.4-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: evolution crash_function: g_malloc executable: /usr/bin/evolution kernel: 3.10.3-300.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 g_malloc at gmem.c:159 #7 g_strdup at gstrfuncs.c:364 #8 internet_address_unformat at camel-internet-address.c:112 #9 camel_search_header_match at camel-search-private.c:490 #10 check_header at camel-folder-search.c:355 #11 camel_sexp_term_eval at camel-sexp.c:812 #12 term_eval_or at camel-sexp.c:376 #13 camel_sexp_term_eval at camel-sexp.c:802 #14 folder_search_match_all at camel-folder-search.c:874 #15 camel_sexp_term_eval at camel-sexp.c:802
Created attachment 782035 [details] File: backtrace
Created attachment 782036 [details] File: cgroup
Created attachment 782037 [details] File: core_backtrace
Created attachment 782038 [details] File: dso_list
Created attachment 782039 [details] File: environ
Created attachment 782040 [details] File: limits
Created attachment 782041 [details] File: maps
Created attachment 782042 [details] File: open_fds
Created attachment 782043 [details] File: proc_pid_status
Created attachment 782044 [details] File: var_log_messages
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions. I see in the backtrace that there happened a memory corruption during message search. I do not know where it happened, as it could be done in any place, even totally unrelated to the search itself. If you have any more insight information, then it'll be helpful. [1] https://bugzilla.gnome.org/show_bug.cgi?id=705472