Bug 1007701

Summary: [abrt] evolution-3.8.5-2.fc19: g_malloc0: Process /usr/libexec/evolution/3.8/evolution-alarm-notify was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: markus.comperini
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: lucilanga, markus.comperini, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:843bddcbe2a1a50c25c8e482e0164b2857a25a50
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-17 05:59:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description markus.comperini 2013-09-13 07:22:51 UTC 
Version-Release number of selected component:
evolution-3.8.5-2.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/3.8/evolution-alarm-notify
crash_function: g_malloc0
executable:     /usr/libexec/evolution/3.8/evolution-alarm-notify
kernel:         3.10.10-200.fc19.x86_64
runlevel:       unknown
uid:            1000

Truncated backtrace:
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
Comment 1 markus.comperini 2013-09-13 07:22:55 UTC 
Created attachment 797176 [details]
File: backtrace
Comment 2 markus.comperini 2013-09-13 07:22:59 UTC 
Created attachment 797177 [details]
File: cgroup
Comment 3 markus.comperini 2013-09-13 07:23:03 UTC 
Created attachment 797178 [details]
File: core_backtrace
Comment 4 markus.comperini 2013-09-13 07:23:10 UTC 
Created attachment 797179 [details]
File: dso_list
Comment 5 markus.comperini 2013-09-13 07:23:14 UTC 
Created attachment 797180 [details]
File: environ
Comment 6 markus.comperini 2013-09-13 07:23:21 UTC 
Created attachment 797181 [details]
File: limits
Comment 7 markus.comperini 2013-09-13 07:23:26 UTC 
Created attachment 797182 [details]
File: maps
Comment 8 markus.comperini 2013-09-13 07:23:30 UTC 
Created attachment 797183 [details]
File: open_fds
Comment 9 markus.comperini 2013-09-13 07:23:33 UTC 
Created attachment 797184 [details]
File: proc_pid_status
Comment 10 markus.comperini 2013-09-13 07:23:36 UTC 
Created attachment 797185 [details]
File: var_log_messages
Comment 11 Milan Crha 2013-09-13 09:44:53 UTC 
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?
Comment 12 markus.comperini 2013-09-13 21:22:46 UTC 
Hello,
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.
Comment 13 Milan Crha 2013-09-16 06:54:18 UTC 
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.
Comment 14 markus.comperini 2013-09-16 08:57:54 UTC 
Hello,
I am sorry, but I can't reproduce this crash with any other notification?
Comment 15 Milan Crha 2013-09-17 05:59:51 UTC 
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.