Abstract
Not all memory leaks are the same. Some eat away at memory slowly over time. Others grab huge chunks of memory all at once. Some memory leaks are caused by the creation of too many objects, others by the way that classes are loaded. What is common for most of them is that they ultimately cause the Java virtual machine's heap to run out of space. A large variety of tools provide a high-level view of a Java application's memory usage, but not all of them are appropriate for doing the detailed analysis needed to find the cause of a memory leak. Depending on the type of memory leak, some tools are more appropriate than others. This session examines some of the tools and techniques available, and uses example memory leaks from real-world Java applications.

Bio
Gregg Sporar has been a software developer for over twenty years, working on projects ranging from control software for a burglar alarm to 3D graphical user interfaces. He has been using Java since 1998 and his interests include user interfaces, development tools, and performance profiling. He works for Sun Microsystems as a Technology Evangelist on the NetBeans project.
 

Meeting Sponsor
Odyssey Information Services provides consulting services for the Information Technology Market. We consistently provide exceptional quality contractors at highly competitive rates. Throughout the last seven years, Odyssey has grown and nurtured relationships with IT managers, our contractors, and even our competitors. We strive to provide the highest quality service to our clients nationwide. Odyssey was founded in 2000, and is headquartered in Dallas, Texas.