>> Why that's my favorite tool for detecting memory leaks of windows.. if the >> numbers keep growing you have a problem.
It does not detect leaks. It reports memory claimed by process. So its usage is limited. It is not useless, but you can't base memory leaks claims on the information it provides. Used memory can grow for different reasons due to memory fragmentation. For example we have an application which loads about 1 GB of data in multiple blocks of different size. Due to user activity it may partially (cause do it in full is slow) unload some data and load another. I've seen memory grew to 1,5 GB after a number of such cycles ( it was still growing and the only limit I can see is 2GB). Code was seriously checked for memory leaks and tested in condition where new memory allocations was avoided between data was loaded/fully unloaded and re-loaded again memory did not grow. Alex On Wed, Oct 3, 2012 at 5:19 AM, Sorvig Morten <morten.sor...@digia.com> wrote: > >>P.S. using Windows Task manager to confirm some memory leaks is seems >>quite stupid to me ;) > > Why that's my favorite tool for detecting memory leaks of windows.. if the > numbers keep growing you have a problem. > > Morten > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
