Description of problem: This time it was NOT - as in most of the cases up to now - , when I pressed "send/receive", but when I clicked on an e-mail I wanted to read. It stood much time advising that it was loading the mail - something evolution does since some weeks, never did it before, but since some time it often takes much time to show the content of an e-mail, and while it is loading I got the message that it was loading the mail - when suddenly evolution crashed. Evolution crashes many many times a day since I have fedora 19 on my pc. It gives or "killed by signal 6", or "killed by signal 11". Version-Release number of selected component: evolution-3.8.3-2.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: evolution crash_function: standard_free executable: /usr/bin/evolution kernel: 3.9.9-302.fc19.i686.PAE runlevel: N 5 uid: 1000 var_log_messages: Jul 21 09:36:23 cp abrt[23526]: Saved core dump of pid 4065 (/usr/bin/evolution) to /var/tmp/abrt/ccpp-2013-07-21-09:36:21-4065 (256335872 bytes) Truncated backtrace: Thread no. 1 (3 frames) #6 standard_free at gmem.c:98 #8 g_source_unref_internal at gmain.c:1993 #13 gtk_main at gtkmain.c:1156
Created attachment 776403 [details] File: backtrace
Created attachment 776404 [details] File: cgroup
Created attachment 776405 [details] File: core_backtrace
Created attachment 776406 [details] File: dso_list
Created attachment 776407 [details] File: environ
Created attachment 776408 [details] File: limits
Created attachment 776409 [details] File: maps
Created attachment 776410 [details] File: open_fds
Created attachment 776411 [details] File: proc_pid_status
Created attachment 776412 [details] File: xsession_errors
Thanks for a bug report. it crashed on a memory corruption, similar as bug #986524. The memory corruption can strike in any places, it depends on the actual memory data being stored there. I'd say once we'll figure out bug #986524, we get this one fixed as well, thus I mark this as a duplicate of the other bug. *** This bug has been marked as a duplicate of bug 986524 ***