Red Hat Bugzilla – Bug 1291116
[abrt] Possible use-after-free on factory subprocess close
Last modified: 2016-04-27 14:04:52 EDT
Version-Release number of selected component:
cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory caldav --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2967x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2967/2
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_mutex_lock at gthread-posix.c:1338
#1 g_main_loop_quit at gmain.c:4059
#2 subprocess_backend_handle_close_cb at evolution-calendar-factory-subprocess.c:99
#3 ffi_call_unix64 at ../src/x86/unix64.S:76
#4 ffi_call at ../src/x86/ffi64.c:525
#5 g_cclosure_marshal_generic at gclosure.c:1487
#8 g_signal_emitv at gsignal.c:3122
#9 _e_dbus_subprocess_backend_skeleton_handle_method_call at e-dbus-subprocess-backend.c:1164
#10 g_dbus_interface_method_dispatch_helper at gdbusinterfaceskeleton.c:609
#11 skeleton_intercept_handle_method_call at gdbusinterfaceskeleton.c:650
Created attachment 1105417 [details]
Created attachment 1105418 [details]
Created attachment 1105419 [details]
Created attachment 1105420 [details]
Created attachment 1105421 [details]
Created attachment 1105422 [details]
Created attachment 1105423 [details]
Created attachment 1105424 [details]
Created attachment 1105425 [details]
Created attachment 1105426 [details]
Created attachment 1105427 [details]
Created attachment 1105428 [details]
Thanks for a bug report. I didn't find anything similar upstream and according to the FAF report this had been reported only once till now. Were you able to reproduce it, please? Maybe the things could change when you updated to the evolution-data-server 3.18.3? There will be an release of 3.18.4 the next week, though it's currently pretty much the same as 3.18.3 in this area, thus it's not needed to wait for the new version.
I see from the backtrace that the crash happened when one of your CalDAV calendars had been closing, but nothing more from it.
(In reply to Milan Crha from comment #13)
> Thanks for a bug report. I didn't find anything similar upstream and
> according to the FAF report this had been reported only once till now. Were
> you able to reproduce it, please? Maybe the things could change when you
> updated to the evolution-data-server 3.18.3? There will be an release of
> 3.18.4 the next week, though it's currently pretty much the same as 3.18.3
> in this area, thus it's not needed to wait for the new version.
> I see from the backtrace that the crash happened when one of your CalDAV
> calendars had been closing, but nothing more from it.
Sorry I can't reproduce. The calendar doesn't really work on Yahoo account. Bugs like this happen during normal operation. Evolution does, Nautilus does, and gnome shell does, transmission does too. I've encountered tons of them, I just click report button as a habit.
Thanks for the update. Regarding the Yahoo! calendar, I managed to figure out what the reason is and filled bug .
The rest depends on various occasions. It's definitely weird to see so many applications crashing.
I will keep this opened, but I'd still need a reproducer to be able to properly identify the cause of the crash.
*** Bug 1331032 has been marked as a duplicate of this bug. ***
I figured that the issue could happen also when the main factory process had been replaced with some other, thena use-after-free on the GMainLoop variable could happen. I fixed this upstream:
Created commit 8568699 in eds master (3.21.2+) 
Created commit c23159f in eds gnome-3-20 (3.20.2+)