Bug 1050992

Summary: [abrt] evolution: g_realloc(): evolution killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Benjamin <b>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: b, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f5401aececae0981632663f009a3de9b4123af9b
Whiteboard: abrt_hash:aeb7a6b995bc0245ccc7c4ac873257d043413bc2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-15 14:54:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Benjamin 2014-01-09 13:30:12 UTC 
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
Comment 1 Benjamin 2014-01-09 13:30:43 UTC 
Created attachment 847647 [details]
File: backtrace
Comment 2 Benjamin 2014-01-09 13:30:47 UTC 
Created attachment 847648 [details]
File: cgroup
Comment 3 Benjamin 2014-01-09 13:30:51 UTC 
Created attachment 847649 [details]
File: core_backtrace
Comment 4 Benjamin 2014-01-09 13:30:54 UTC 
Created attachment 847650 [details]
File: dso_list
Comment 5 Benjamin 2014-01-09 13:30:56 UTC 
Created attachment 847651 [details]
File: environ
Comment 6 Benjamin 2014-01-09 13:30:58 UTC 
Created attachment 847652 [details]
File: exploitable
Comment 7 Benjamin 2014-01-09 13:31:02 UTC 
Created attachment 847653 [details]
File: limits
Comment 8 Benjamin 2014-01-09 13:31:06 UTC 
Created attachment 847654 [details]
File: maps
Comment 9 Benjamin 2014-01-09 13:31:09 UTC 
Created attachment 847655 [details]
File: open_fds
Comment 10 Benjamin 2014-01-09 13:31:11 UTC 
Created attachment 847656 [details]
File: proc_pid_status
Comment 11 Benjamin 2014-01-09 13:31:15 UTC 
Created attachment 847657 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-01-15 14:51:44 UTC 
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).
Comment 13 Milan Crha 2014-01-15 14:54:08 UTC 
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 ***
Comment 14 Benjamin 2014-01-15 17:48:30 UTC 
I've put my comment into the other bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=1047529#c16