Debugging memory leaks

This section begins with a discussion of the Windows memory model and the Java™ heap to provide background understanding before going into the details of memory leaks.

The Windows memory model
Windows memory is virtualized. Applications do not have direct access to memory addresses, so allowing Windows to move physical memory and to swap memory in and out of a swapper file (called pagefile.sys).
Classifying leaks
You can classify memory leaks from the usage of Windows memory and the size of the Java heap.
Tracing leaks
Some useful techniques for tracing leaks are built into the JVM.
Using Heapdump to debug memory leaks
You can use Heapdump to analyze the Java Heap.

Parent topic: Windows problem determination