dx-packages team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version. When you test
it and it is still an issue, kindly upload the updated logs by running
apport-collect <bug #> and any other logs that are relevant for this
particular issue.

For what it's worth, I'm not seeing these leaks in my own testing when
running valgrind on the latest version of indicator-datetime,
13.10.0+14.04.20140227.1-0ubuntu1

** Changed in: indicator-datetime (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/829967

Title:
  indicator-datetime leaks memory

Status in “indicator-datetime” package in Ubuntu:
  Incomplete

Bug description:
  While monitoring some processes to find another leak, I found
  indicator-datetime to constantly use more (resident) memory over time
  (see screenshot). Over 10 hours of the system idling, the process
  gained 5MB which is kind of unacceptable on long running systems
  (given that stays linear while the system is in use - I'm checking
  that today).

  Will add valgrind information shortly.

  This bug seems to be different from bug 782468, as I don't see that
  much of an increase. I've not added any additional timezones or
  anything like that.

  Using indicator-application 0.2.93-0ubuntu1 on up-to-date Oneiric.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/829967/+subscriptions