Bug 991520 - [abrt] evolution-3.8.4-1.fc19: g_malloc: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
[abrt] evolution-3.8.4-1.fc19: g_malloc: Process /usr/bin/evolution was kille...
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
19
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
abrt_hash:44d592d4adf09546baacf93d618...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-02 12:04 EDT by Louis van Dyk
Modified: 2013-08-05 01:18 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-05 01:18:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (69.39 KB, text/plain)
2013-08-02 12:05 EDT, Louis van Dyk
no flags Details
File: cgroup (140 bytes, text/plain)
2013-08-02 12:05 EDT, Louis van Dyk
no flags Details
File: core_backtrace (3.86 KB, text/plain)
2013-08-02 12:05 EDT, Louis van Dyk
no flags Details
File: dso_list (11.91 KB, text/plain)
2013-08-02 12:05 EDT, Louis van Dyk
no flags Details
File: environ (1.74 KB, text/plain)
2013-08-02 12:05 EDT, Louis van Dyk
no flags Details
File: limits (1.29 KB, text/plain)
2013-08-02 12:05 EDT, Louis van Dyk
no flags Details
File: maps (156.52 KB, text/plain)
2013-08-02 12:05 EDT, Louis van Dyk
no flags Details
File: open_fds (3.27 KB, text/plain)
2013-08-02 12:05 EDT, Louis van Dyk
no flags Details
File: proc_pid_status (948 bytes, text/plain)
2013-08-02 12:05 EDT, Louis van Dyk
no flags Details
File: var_log_messages (17.94 KB, text/plain)
2013-08-02 12:06 EDT, Louis van Dyk
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 705472 None None None Never

  None (edit)
Description Louis van Dyk 2013-08-02 12:04:55 EDT
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
Comment 1 Louis van Dyk 2013-08-02 12:05:00 EDT
Created attachment 782035 [details]
File: backtrace
Comment 2 Louis van Dyk 2013-08-02 12:05:06 EDT
Created attachment 782036 [details]
File: cgroup
Comment 3 Louis van Dyk 2013-08-02 12:05:10 EDT
Created attachment 782037 [details]
File: core_backtrace
Comment 4 Louis van Dyk 2013-08-02 12:05:16 EDT
Created attachment 782038 [details]
File: dso_list
Comment 5 Louis van Dyk 2013-08-02 12:05:20 EDT
Created attachment 782039 [details]
File: environ
Comment 6 Louis van Dyk 2013-08-02 12:05:25 EDT
Created attachment 782040 [details]
File: limits
Comment 7 Louis van Dyk 2013-08-02 12:05:48 EDT
Created attachment 782041 [details]
File: maps
Comment 8 Louis van Dyk 2013-08-02 12:05:52 EDT
Created attachment 782042 [details]
File: open_fds
Comment 9 Louis van Dyk 2013-08-02 12:05:56 EDT
Created attachment 782043 [details]
File: proc_pid_status
Comment 10 Louis van Dyk 2013-08-02 12:06:00 EDT
Created attachment 782044 [details]
File: var_log_messages
Comment 11 Milan Crha 2013-08-05 01:18:53 EDT
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

Note You need to log in before you can comment on or make changes to this bug.