Making a selection in the List of events while thousands of events are loading will cause an application freeze with 100% CPU usage on a single thread
With Evolution 3.50.0, when testing for another issue in the Calendar module, I made the mistake of:
- selecting my Google account's primary calendar, which has accumulated roughly 3300 events events over the last 15+ years,
- selecting one of its items "too soon" while it was loading/processing the events
More specifically, my reproduction steps are:
- Start Evolution's Calendar, switch to List view mode (
Ctrl+L
) - Select a calendar with not too many events
- Select a calendar with lots (3000+) of events
- Immediately click one of the events once to select it, and a second time to enter text cursor editing mode (I don't actually use this mode, I'd much rather open the event editor dialog, but for the sake of testing...)
The result is that Evolution hogs 100% of one of my logical CPU cores at a time (the 7 others are left unused), and the UI becomes unresponsive (GNOME Shell / Mutter frequently proposes to "Force Quit" the app).
I've tested this on the Wayland version of GNOME Shell in Fedora 39.
Edited by Jeff Fortin