Comment 9 for bug 1633319

Revision history for this message
Jonathan Brier (brierjon) wrote :

I've been able to narrow down on my system that enabling "Evolution Data Server" for Access to the Google Calendar is the trigger for this memory issue. See the three screenshots. I even removed and reauthorized the Google account access with no change.

First screenshot shows the Evolution Data Service disabled and memory function is normal.
Second is toggling the Evolution Data Service from off to on. After ~10-5 seconds memory consumption appears at a rapid rate.
Third is after switching Evolution Data Service from on to off and killing the indicator-datetime-service process showing the memory issue no longer exists.

If Evolution Data Server is not switched to off killing the indicator-datetime-service process only restarts memory levels at the initial value and consumption growth appears nearly immediately following its automatic resume.