Red Hat Bugzilla – Bug 1025732
[abrt] evolution-3.11.1-1.fc21: g_type_check_instance: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2016-07-19 06:32:51 EDT
Description of problem:
Crashed on uploading a photo to a contact in Google Addressbook with resize
Version-Release number of selected component:
runlevel: N 3
Thread no. 1 (10 frames)
#0 g_type_check_instance at gtype.c:4082
#1 g_signal_handler_disconnect at gsignal.c:2580
#2 e_alert_run_dialog at e-alert-dialog.c:361
#3 e_alert_run_dialog_for_args at e-alert-dialog.c:384
#8 eab_editor_contact_modified at eab-editor.c:383
#9 contact_modified_cb at e-contact-editor.c:3632
#10 contact_modified_ready_cb at e-contact-editor.c:3658
#11 g_simple_async_result_complete at gsimpleasyncresult.c:777
#12 complete_in_idle_cb_for_thread at gsimpleasyncresult.c:845
#17 gtk_main at gtkmain.c:1158
Created attachment 818264 [details]
Created attachment 818265 [details]
Created attachment 818266 [details]
Created attachment 818267 [details]
Created attachment 818268 [details]
Created attachment 818269 [details]
Created attachment 818270 [details]
Created attachment 818271 [details]
Created attachment 818272 [details]
Created attachment 818273 [details]
Thanks for a bug report. Do you have any exact steps for a reproducer, please? I'd guess there is a use-after-free issue involved here, which might not always crash, but could be noticeable by valgrind.
Interesting, the steps are identical to https://bugzilla.gnome.org/show_bug.cgi?id=708166, but the crashing function here is different. I presume both these crashes are caused by one race condition in updating/deleting attributes
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.