indicator-datetime uses 80% of RAM or 3.1g

[Alex Mayorga]

System was running slow, ran top and found indicator-datetime hogging RAM, used ubuntu-bug to file this report prior to killing the process.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: indicator-datetime 0.3.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
Uname: Linux 3.2.0-6-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CheckboxSubmission: ed5dbdfb54bf5043a043813a33527c9f
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
Date: Tue Dec 20 12:09:12 2011
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: indicator-datetime
UpgradeStatus: Upgraded to precise on 2011-12-17 (2 days ago)

[Alex Mayorga (alex-mayorga)]

Perhaps related to the fact that the alternate locations fail to show on the time & date applet, it flashes for a split second, but only the main one is actually visible.

Attached the list of alternate locations, the main location is set to Monterrey, Mexico.

[Charles Kerr (charlesk)]

That's a lot of memory :-)

If you could grab a profile with Valgrind that would be a big help in getting it fixed. Thanks!

https://wiki.ubuntu.com/Valgrind

[Alex Mayorga (alex-mayorga)]

The problem is this is a service not an actual program, so I don't know where to start.

Asking on IRC I now know that /usr/share/dbus-1/services/indicator-datetime.service is the file that actually launches the service.

The original contents were:

[D-BUS Service]
Name=com.canonical.indicator.datetime
Exec=/usr/lib/indicator-datetime/indicator-datetime-service

I modified it to:

[D-BUS Service]
Name=com.canonical.indicator.datetime
Exec=G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=/home/alex-mayorga/valgrind.log /usr/lib/indicator-datetime/indicator-datetime-service

Then killed the leaking service but then it failed to restart, pretty sure I'm doing it wrong but I don't know what exactly =(

[Alex Mayorga (alex-mayorga)]

Finally got a couple of valgrind results thanks to this changes on /usr/share/dbus-1/services/indicator-datetime.service suggested by trism on #ubuntu+1

[D-BUS Service]
Name=com.canonical.indicator.datetime
#Exec=/usr/lib/indicator-datetime/indicator-datetime-service
Exec=/bin/bash -c '/usr/bin/valgrind --leak-check=full --log-file=/tmp/indicator-datetime-$(date +%H-%M-%S).log /usr/lib/indicator-datetime/indicator-datetime-service'

[Jason Conti (jconti)]

Do you have any geoclue providers other then geoclue-ubuntu-geoip installed? It would be interesting to see the output of:

dpkg -l '*geoclue*'

I only ask because of a recent report from a user who was seeing high-cpu usage from indicator-datetime-service when geoclue-yahoo was installed, thought this might be a similar situation.

[Alex Mayorga (alex-mayorga)]

Jason,

thanks in the lead.
Here's the output:

alex-mayorga@VPCCW1FFXL:~$ dpkg -l '*geoclue*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii geoclue 0.12.0-1ubuntu Geographic information framework
un geoclue-provid <none> (no description available)
un geoclue-ubuntu <none> (no description available)
ii geoclue-yahoo 0.12.0-1ubuntu Map and geocode server for GeoClue (Yahoo)
ii libgeoclue0 0.12.0-1ubuntu C API for GeoClue

Anything I should remove?

[Jason Conti (jconti)]

Yes, install geoclue-ubuntu-geoip and then remove geoclue-yahoo. This is related to bug #919364

[Alex Mayorga (alex-mayorga)]

Thanks! This has apparently fixed the high memory usage.

Now I have an alternate clock I've never configured. What's the file that controls the alternate clocks? Seems like I need to do a bit of cleanup there.

I suspect bug #918546 it's a duplicate of this one.

[Bilal Akhtar (bilalakhtar)]

Invalid, as you've already found out that this isn't indicator-datetime's fault.