Rich-client application performance, Part 2, Plugging memory leaks
From the developerWorks archives
Date archived: January 9, 2017 | First published: August 07, 2007
Part 1 of this two-part article on Eclipse rich-client performance covers the basics of measuring an application's performance, applying instrumentation techniques, keeping the UI responsive, and using
Jobs to avoid threading mistakes. This second part takes a look at memory usage and how to chase down memory leaks.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.