Version-Release number of selected component: evolution-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: evolution crash_function: g_realloc executable: /usr/bin/evolution kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 g_realloc at gmem.c:169 #4 g_ptr_array_maybe_expand at garray.c:1111 #5 g_ptr_array_sized_new at garray.c:910 #6 vee_folder_subfolder_changed at camel-vee-folder.c:408 #7 vee_folder_process_changes at camel-vee-folder.c:499 #8 session_do_job_cb at camel-session.c:175 #9 run_in_thread at gsimpleasyncresult.c:871 #10 io_job_thread at gioscheduler.c:89 #11 g_task_thread_pool_thread at gtask.c:1245 #13 g_thread_proxy at gthread.c:798
Created attachment 847647 [details] File: backtrace
Created attachment 847648 [details] File: cgroup
Created attachment 847649 [details] File: core_backtrace
Created attachment 847650 [details] File: dso_list
Created attachment 847651 [details] File: environ
Created attachment 847652 [details] File: exploitable
Created attachment 847653 [details] File: limits
Created attachment 847654 [details] File: maps
Created attachment 847655 [details] File: open_fds
Created attachment 847656 [details] File: proc_pid_status
Created attachment 847657 [details] File: var_log_messages
Thanks for a bug report. This seems to be caused by evolution getting out of memory, if I read an attachment at comment #10 properly. To help identify the part which probably doesn't free memory properly, could you provide some details about your evolution settings, please? I see from the backtrace that you have configured at least one IMAP+ account, do you have any other account types configured too? Do you use Contacts and Calendar features of evolution? Did evolution run for a long time (several hours or several days), before it crashed? I guess there is some place which leaks, and the duration of running evolution depends on the frequency of the leaking place being called (most likely multiple places, not only one).
Ouch, I just noticed that I have a similar bug report here already, thus I'm marking this as a duplicate of it. Feel free to provide the information here, or you can there, I'm fine with both variants. *** This bug has been marked as a duplicate of bug 1047529 ***
I've put my comment into the other bug report. https://bugzilla.redhat.com/show_bug.cgi?id=1047529#c16