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.

Note

You need to
log in
before you can comment on or make changes to this bug.