Description of problem: I had a mail message with a calendar entry that wasn't in any of my calendars. It searched and didn't find them. I wanted to change to an Exchange-EWS calendar, so I pulled it down and selected it in the dropdown. As soon as I changed the calendar in the drop-down, evo crashed. I was able to repeat this multiple times. I added the calendar entry from my phone to the exchange calendar and now evo finds it and doesn't crash. Version-Release number of selected component: evolution-3.10.4-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: evolution crash_function: g_type_check_instance_is_a executable: /usr/bin/evolution kernel: 3.14.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 9661 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_a at gtype.c:3975 #1 itip_view_ref_source at itip-view.c:2600 #2 source_changed_cb at itip-view.c:833 #3 WebCore::GObjectEventListener::handleEvent at Source/WebCore/bindings/gobject/GObjectEventListener.cpp:67 #4 WebCore::EventTarget::fireEventListeners at Source/WebCore/dom/EventTarget.cpp:246 #6 WebCore::EventContext::handleLocalEvents at Source/WebCore/dom/EventContext.cpp:58 #7 dispatchEventAtTarget at Source/WebCore/dom/EventDispatcher.cpp:161 #8 WebCore::EventDispatcher::dispatch at Source/WebCore/dom/EventDispatcher.cpp:118 #9 WebCore::EventDispatcher::dispatchEvent at Source/WebCore/dom/EventDispatcher.cpp:52 #10 WebCore::ScopedEventQueue::dispatchEvent at Source/WebCore/dom/ScopedEventQueue.cpp:84
Created attachment 916392 [details] File: backtrace
Created attachment 916393 [details] File: cgroup
Created attachment 916394 [details] File: core_backtrace
Created attachment 916395 [details] File: dso_list
Created attachment 916396 [details] File: environ
Created attachment 916397 [details] File: exploitable
Created attachment 916398 [details] File: limits
Created attachment 916399 [details] File: maps
Created attachment 916400 [details] File: open_fds
Created attachment 916401 [details] File: proc_pid_status
Created attachment 916402 [details] File: var_log_messages
Thanks for a bug report. I do not recall seeing any similar crash myself, and the search in an upstream bugzilla (GNOME's bugzilla) also doesn't return any hits for the last two years, thus it seems to me like you your environment behaves in a way which the itip-formatter (the part of the code responsible of the meeting invitations handling) doesn't work properly. Could you try to install valgrind, then run evolution under it, to see whether it'll show where the memory got freed, please? Evolution will be very slow, due to all the memory checking, thus just try to reproduce the issue and close evolution. it can also happen that the evolution will not crash this time, it can be due to the valgrind catching the error and avoiding the crash, in which case it logs about the issue instead. The command to use is: $ G_SLICE=always-malloc valgrind --num-callers=20 evolution &>log.txt
I will attempt to do so. I added the calendar entry through my phone so it stopped asking about it because it's in the calendar now. I'll see if I can remove the calendar entry and try again, but in the past I've had issues removing entries. I can send you the calendar invitation if it would help?
(In reply to Derek Atkins from comment #13) > I can send you the calendar invitation if it would help? Not needed, thanks. I hoped you'll be quicker with the valgrind log, because I seem to be currently busy with some other stuff.
I'm afriad at this point I've upgraded to 3.12.14 so I wont be able to help you track this down. Sorry.
That's even better, using more recent code is appreciated. Feel free to reopen in case you'll face it with 3.12.x or simply file a new bug report. Thanks in advance.