Bug 1058787 - [abrt] evolution: g_malloc0(): evolution killed by SIGABRT
Summary: [abrt] evolution: g_malloc0(): evolution killed by SIGABRT
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:da67b6b3d6688ca4fc5746bff1f...
: 1058825 1059779 1060431 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-28 14:19 UTC by bpk678
Modified: 2014-02-03 08:32 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-30 07:40:47 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (66.91 KB, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
File: cgroup (172 bytes, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
File: core_backtrace (47.88 KB, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
File: dso_list (25.84 KB, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
File: environ (1.42 KB, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
File: limits (1.29 KB, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
File: maps (163.22 KB, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
File: open_fds (1.29 KB, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
File: proc_pid_status (970 bytes, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
File: var_log_messages (17.20 KB, text/plain)
2014-01-28 14:19 UTC, bpk678 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 709554 0 None None None Never

Description bpk678 2014-01-28 14:19:03 UTC 
Version-Release number of selected component:
evolution-3.10.3-1.fc20

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        evolution
crash_function: g_malloc0
executable:     /usr/bin/evolution
kernel:         3.12.8-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 g_malloc0 at gmem.c:134
 #7 camel_imapx_command_add_part at camel-imapx-command.c:522
 #8 camel_imapx_command_close at camel-imapx-command.c:549
 #9 imapx_command_queue at camel-imapx-server.c:1316
 #10 imapx_command_run_sync at camel-imapx-server.c:3009
 #11 imapx_job_refresh_info_start at camel-imapx-server.c:5752
 #12 camel_imapx_job_run at camel-imapx-job.c:255
 #13 camel_imapx_server_refresh_info at camel-imapx-server.c:7652
 #14 imapx_refresh_info_sync at camel-imapx-folder.c:676
 #15 camel_folder_refresh_info_sync at camel-folder.c:4209
Comment 1 bpk678 2014-01-28 14:19:12 UTC 
Created attachment 856607 [details]
File: backtrace
Comment 2 bpk678 2014-01-28 14:19:14 UTC 
Created attachment 856608 [details]
File: cgroup
Comment 3 bpk678 2014-01-28 14:19:16 UTC 
Created attachment 856609 [details]
File: core_backtrace
Comment 4 bpk678 2014-01-28 14:19:21 UTC 
Created attachment 856610 [details]
File: dso_list
Comment 5 bpk678 2014-01-28 14:19:23 UTC 
Created attachment 856611 [details]
File: environ
Comment 6 bpk678 2014-01-28 14:19:24 UTC 
Created attachment 856612 [details]
File: limits
Comment 7 bpk678 2014-01-28 14:19:29 UTC 
Created attachment 856613 [details]
File: maps
Comment 8 bpk678 2014-01-28 14:19:32 UTC 
Created attachment 856614 [details]
File: open_fds
Comment 9 bpk678 2014-01-28 14:19:34 UTC 
Created attachment 856615 [details]
File: proc_pid_status
Comment 10 bpk678 2014-01-28 14:19:36 UTC 
Created attachment 856616 [details]
File: var_log_messages
Comment 11 Milan Crha 2014-01-30 07:40:47 UTC 
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

The application crashed due to memory corruption (some part of the code accesses already freed memory or wrote to place where it should not, most likely, overwriting part of some memory where was residing some other data), but it's quite hard to find such issues without any clue where to look, because the overwritten memory can be accessed any time later. Do you remember what you did in evolution before the crash happened, please? It might not be right before the crash.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=709554
Comment 12 Milan Crha 2014-01-30 07:43:44 UTC 
*** Bug 1058825 has been marked as a duplicate of this bug. ***
Comment 13 Milan Crha 2014-01-31 07:03:35 UTC 
*** Bug 1059779 has been marked as a duplicate of this bug. ***
Comment 14 Milan Crha 2014-02-03 08:32:53 UTC 
*** Bug 1060431 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.