Comment 3 for bug 974382

I disagree with the response here for the following reasons:
 * marking it 'invalid' so it will magically go away isn't helpful for anyone
 * suggesting that I should log out of my currently running environment, and run valgrind on my system for the next 2 weeks because you find that unreasonable to do yourself is somewhat rude
 * marking a memory leak of 420M over 3 weeks as 'low' is troubling.

You probably will get your desired result of making this bug go away, as I'm not likely to run my desktop under valgrind for a extended period of time.

I realize that the bug was reported against old versions, and understand the desire to see if it is still relevant.

My currently running environment has unity-panel-service up for ~ 10 days and it has a footprint of 42M (per top) at the moment. I believe that likely there is still a leak shown there. However, it was not being used for a significant portion of that as I was travelling. So, my finger-in-the-wind assessment is that you have fixed some memory leaks, but that it is still leaking. Again, having run the desktop for 10 days, my running versions are out of date, so even that data is not 100% relevant any more.

I really would feel much better if you were running valgrind in some automated fashion for extended periods of time on the components of Unity.