Red Hat Bugzilla – Bug 821517
[abrt] evolution-3.2.3-3.fc16: _int_free: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2013-02-13 12:40:39 EST
libreport version: 2.0.8
comment: I was opaning evolution and it crashed.
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
time: Mon 14 May 2012 06:58:34 AM MST
backtrace: Text file, 45382 bytes
build_ids: Text file, 7216 bytes
dso_list: Text file, 17132 bytes
maps: Text file, 51199 bytes
xsession_errors: Text file, 6011 bytes
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:May 14 06:58:34 home kernel: [887103.043943] evolution: segfault at 3732333d ip 44619200 sp bf978730 error 4 in libc-2.14.90.so[445a2000+1a7000]
:May 14 06:58:35 home abrt: Saved core dump of pid 5894 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2012-05-14-06:58:34-5894 (65552384 bytes)
Created attachment 584432 [details]
Created attachment 584433 [details]
Created attachment 584434 [details]
Created attachment 584435 [details]
Created attachment 584436 [details]
Thanks for a bug report. This looks like a memory corruption bug, which use to be hard to reproduce. I see in the backtrace that there happened some change in On This Computer/Inbox/Bluemaumau folder, which was about to propagate further, but it suddenly failed in memory free function. The reason for this failure can be basically anything, thus it's hard to address without steps to reproduce.
Are you able to reproduce this, please? Does it help to run evolution like this to reproduce it:
$ G_SLICE=always-malloc,debug-blocks evolution
Thread 1 (Thread 0xb76f18c0 (LWP 5894)):
#0 0x44619200 in malloc_consolidate (av=0x4474c3e0) at malloc.c:4266
#1 0x44619e83 in malloc_consolidate (av=0x4474c3e0) at malloc.c:4227
#2 _int_free (av=0x4474c3e0, p=<optimized out>, have_lock=0) at malloc.c:4158
#3 0x446adcc1 in __GI___vasprintf_chk (result_ptr=0xbf97892c, flags=1, format=0xb6157903 "folder://%s/%s", args=0xbf978964 "") at vasprintf_chk.c:86
#4 0x4996cef7 in vasprintf (__ap=0xbf978964 "", __fmt=0xb6157903 "folder://%s/%s", __ptr=0xbf97892c) at /usr/include/bits/stdio2.h:199
#5 g_vasprintf (string=0xbf97892c, format=0xb6157903 "folder://%s/%s", args=0xbf978964 "") at gprintf.c:314
#6 0x49945b64 in g_strdup_vprintf (format=0xb6157903 "folder://%s/%s", args=0xbf978964 "") at gstrfuncs.c:253
#7 0x49945b94 in g_strdup_printf (format=0xb6157903 "folder://%s/%s") at gstrfuncs.c:279
#8 0xb60e90ed in e_mail_folder_uri_build (store=0x9e4b3a8, folder_name=<optimized out>) at e-mail-folder-utils.c:1399
#9 0xb60e1cbc in mail_backend_folder_changed_cb (folder_cache=0xa045c48, store=0x9e4b3a8, folder_name=0xa1dc4d0 "Inbox/Bluemaumau", new_messages=0, msg_uid=0x0, msg_sender=0x0, msg_subject=0x0, shell=0x9e2a800) at e-mail-backend.c:551
#10 0x4c1d148e in e_marshal_VOID__OBJECT_STRING_INT_STRING_STRING_STRING (closure=0xa10e938, return_value=0x0, n_param_values=7, param_values=0x9e2ab60, invocation_hint=0xbf978b30, marshal_data=0x0) at e-marshal.c:1871
#11 0x49820655 in g_closure_invoke (closure=0xa10e938, return_value=0x0, n_param_values=7, param_values=0x9e2ab60, invocation_hint=0xbf978b30) at gclosure.c:774
#12 0x49833870 in signal_emit_unlocked_R (node=0xa0fc880, detail=0, instance=0xa045c48, emission_return=0x0, instance_and_params=0x9e2ab60) at gsignal.c:3272
#13 0x4983c30f in g_signal_emit_valist (instance=0xa045c48, signal_id=251, detail=0, var_args=0xbf978d04 "\364?\240Ip*n\n\330&\222Ip*n\n`H]\n\271\034\024\266\364?\240Ip\262J\n\220\215\227\277<") at gsignal.c:3003
#14 0x4983c474 in g_signal_emit (instance=0xa045c48, signal_id=251, detail=0) at gsignal.c:3060
#15 0xb6141d93 in flush_updates_idle_cb (self=0xa045c48) at mail-folder-cache.c:180
#16 0x49922941 in g_idle_dispatch (source=0xa4ab270, callback=0xb6141cb0 <flush_updates_idle_cb>, user_data=0xa045c48) at gmain.c:4801
#17 0x49926aff in g_main_dispatch (context=0x9d80268) at gmain.c:2441
#18 g_main_context_dispatch (context=0x9d80268) at gmain.c:3011
#19 0x49927240 in g_main_context_iterate (context=0x9d80268, block=1234394384, dispatch=1, self=0x9d4e4d8) at gmain.c:3089
#20 0x49927877 in g_main_loop_run (loop=0xa10aba0) at gmain.c:3297
#21 0x4d2dc2d5 in gtk_main () at gtkmain.c:1362
#22 0x08049cb7 in main (argc=1, argv=0xbf978fc4) at main.c:709
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.