Finding the cause of memory leaks can be very tricky, and tracking down complex leaks frequently involves using several tools in conjunction. The application is somehow keeping references to objects that should no longer be in use. What's worse, the place in the code where the leaked instance was allocated does not necessarily have to be co-located with the place in the code pertaining to the leak. We need to analyze the heap to find out what is going on.
To start Memleak, simply select the JVM to connect to in the JVM Browser and choose Memleak from the context menu.
Only one Memleak instance can be connected to any given JVM at a time.
In Memleak, the trend table can help detect even slow leaks. It does this by building ...