Red Hat Bugzilla – Bug 1464136
[abrt] evolution-data-server: g_type_check_instance_is_fundamentally_a(): evolution-calendar-factory-subprocess killed by signal 11
Last modified: 2018-05-29 07:29:31 EDT
Version-Release number of selected component:
cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx1999x5 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/1999/5
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_type_check_instance_is_fundamentally_a at gtype.c:4025
#2 cal_backend_sexp_finalize at /usr/src/debug/evolution-data-server-3.24.2/src/calendar/libedata-cal/e-cal-backend-sexp.c:1103
#4 data_cal_view_dispose at /usr/src/debug/evolution-data-server-3.24.2/src/calendar/libedata-cal/e-data-cal-view.c:434
#6 e_cal_backend_remove_view at /usr/src/debug/evolution-data-server-3.24.2/src/calendar/libedata-cal/e-cal-backend.c:1441
#7 impl_DataCalView_dispose at /usr/src/debug/evolution-data-server-3.24.2/src/calendar/libedata-cal/e-data-cal-view.c:265
#8 ffi_call_unix64 at ../src/x86/unix64.S:76
#9 ffi_call at ../src/x86/ffi64.c:525
#10 g_cclosure_marshal_generic at gclosure.c:1490
#15 e_gdbus_stub_handle_method_call at /usr/src/debug/evolution-data-server-3.24.2/src/libedataserver/e-gdbus-templates.c:677
#16 call_in_idle_cb at gdbusconnection.c:4850
Created attachment 1290714 [details]
Created attachment 1290715 [details]
Created attachment 1290716 [details]
Created attachment 1290717 [details]
Created attachment 1290718 [details]
Created attachment 1290719 [details]
Created attachment 1290720 [details]
Created attachment 1290721 [details]
Created attachment 1290722 [details]
Created attachment 1290723 [details]
Created attachment 1290724 [details]
Created attachment 1290725 [details]
Thanks for a bug report. I see from the backtrace that this crashed when one of your EWS calendars had been notified about no longer active view. It can happen from anywhere, including GNOME Shell's calendar server, like when moving between days to show (in any calendar application which uses evolution-data-server, not only in GNOME Shell). The pointer address it crashed with is used in another thread as well, by libsoup. It can be that there's some ref/unref imbalance somewhere in the code, either directly in evolution-ews, or in evolution-data-server or even in libsoup. It's hard to tell from the backtrace. I'll check the usage of this object in the code, but if it broke due to some other code writing to already freed memory, thus effectively overwriting memory it didn't belong to it any more, then it'll be quite hard to find it (because it could be just a coincidence that it touched this object).
I checked the code, but I didn't find anything obvious. The object in question is a private member, and the places where it is exposed look fine (by code reading). Unless the impl_DataCalView_dispose() being called twice for one view I'd say there is not much chance that this could happen in properly running environment (with that I mean that the code looks correct, thus it's possible that the problem is about some use-after-free or similar issue, something touching code it should not).
Having a reproducer would be a good start, but as such issues are pretty hard to spot (and they tend to strike on different place each time) I'm afraid we have bad luck.
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora 'version'
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 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 change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.