| 2011-08-20 12:17:33 |
Hernando Torque |
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).
I need instructions on how to get you more useful information. I know about valgrind, but I'm not sure how to use it to find what's causing this memory loss over time (should a simple start of the indicator under valgrind be enough or do I need to let it run all the time?).
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. |
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. |
|
