Indicator-datetime-service renders 25% CPU usage and 100% RAM

[Anders Hall]

Same as Bug #774071 but with 100% RAM instead. Collected info while the Indicator-datetime-service was acting up. I.e., writing this with a few hundred megabytes RAM available..

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Nov 13 15:41:39 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2015-07-18 (848 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: indicator-datetime
UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago)

[Anders Hall (a.hall)]

PID changes after crash when RAM is depleted. Sceenshoot of RAM usage attached.

[Anders Hall (a.hall)]

Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show a clock in the menu bar" in System Settings for Time & Date. Worked after cold reboot.

[Anders Hall (a.hall)]

Last work-around didn't stick. Did some test and can reproduce the error now easily in 17.04. Ubuntu reports it is the Indicator-datetime-service that crashes when its the evolution calendar that is the problem. During the system overload the problem can be fixed by killing all evolution processes and sub-processes indirectly.

Evolution is overloading the Indicator-datetime-service somehow with lots of (factory?) sub-processes.

Attached screenshot of the processes active during the error. Resolved by killing the evolution processes in the screenshot.

Also, this problem started after enabling Empathy on boot. However, after disabling Empathy completely at startup the problem persisted.

Will update to 17.10 (KVM bug fixed) and see if the error is unresolved.

[Anders Hall (a.hall)]

The problem went away in 17.10. Cheers.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.