Red Hat Bugzilla – Bug 1007701
[abrt] evolution-3.8.5-2.fc19: g_malloc0: Process /usr/libexec/evolution/3.8/evolution-alarm-notify was killed by signal 6 (SIGABRT)
Last modified: 2013-09-17 01:59:51 EDT
Version-Release number of selected component:
Thread no. 1 (10 frames)
#7 g_malloc0 at gmem.c:189
#8 _gtk_css_lookup_new at gtkcsslookup.c:33
#9 build_properties at gtkstylecontext.c:991
#10 style_data_lookup at gtkstylecontext.c:1037
#11 _gtk_style_context_validate at gtkstylecontext.c:3240
#16 gtk_container_idle_sizer at gtkcontainer.c:1654
#17 _g_closure_invoke_va at gclosure.c:840
#19 g_signal_emit_by_name at gsignal.c:3424
#20 gdk_frame_clock_paint_idle at gdkframeclockidle.c:400
#26 g_main_context_iteration at gmain.c:3762
Created attachment 797176 [details]
Created attachment 797177 [details]
Created attachment 797178 [details]
Created attachment 797179 [details]
Created attachment 797180 [details]
Created attachment 797181 [details]
Created attachment 797182 [details]
Created attachment 797183 [details]
Created attachment 797184 [details]
Created attachment 797185 [details]
Thanks for a bug report. I see from the val_log_messages that this crashed due to a memory corruption. By any chance, do you have any steps to be able to reproduce this, please? Or at least some hints what was happening before the crash? I suppose, as this is an alarm notification process, you most likely received a notification for some upcoming event, and this either crashed when this was going to show itself to you, or you dismissed the notification, or something like that?
I had an appointment, which was shown by the evolution-package.
I opened this message, set the appointment to ignore and close it.
Then it crashed.
Thanks for the update. It sounds like a usual work with the alarm notifications. Were you able to reproduce this with any other meeting notification? Also, do you remember what appointment event was in the dialog? Maybe its content will help to reproduce the crash.
I am sorry, but I can't reproduce this crash with any other notification?
Thanks for the update. That's OK, I know such memory corruption bugs are pretty hard to reproduce consistently. Let me close this bug for now, but keep watching for any duplicates.