A call to test, fix for lp:501486

0 views

Skip to first unread message

Chris Szikszoy

unread,

Apr 7, 2010, 4:17:32 AM4/7/10

to Docky

Hi All,

I recently pushed some fixes to our only "critical" bug,
https://bugs.edge.launchpad.net/docky/+bug/501486 . Please update to
the latest bzr revision and do some longterm testing to verify that
memory usage does not continually climb. We're planning to get this
into the lucid package and it would be nice to hear from some testers
if this does indeed fix our memory leak.

Thanks,
- Chris S.

Robert Dyer

unread,

Apr 7, 2010, 1:05:39 PM4/7/10

to docky...@googlegroups.com

Thanks for your hard work on this Chris!

I am sad to report however that this does not solve the memory leaks. It may (and probably does) *help* with them, but there are still plenty of leaks.

It is hard to estimate how long Docky has been running since I pulled in your leak fixes last night (because I suspended), but when initially launched Docky was at around 35mb for me. It is currently at 50mb. I will try to continue running it for the rest of the day without a restart and see if we get above 100mb.

I used to routinely see Docky at 150mb usage, but never really bothered to track down how long it took to get there - it just seemed like roughly 24 hrs.

- Robert