Memory

JVM Memory & Garbage Collection Tools

OutOfMemoryError reports, growing heap graphs in your monitoring, and slowly-rotting response times are usually signs one of two things: a leak, or excessive garbage-collection pressure. The tools in this category are how you turn those symptoms into an exact cause.

Two distinct workflows matter here. Heap-dump analysis answers 'what is holding onto this memory' (Eclipse MAT, jmap -dump). GC log / GC behavior analysis answers 'why is the collector working so hard' (GCViewer, gceasy, -Xlog:gc). Most teams need both.

What you'll find here: Capture a heap dump: jmap -dump:live, /diagnostic/jmap/status · Find leaks & dominators with Eclipse MAT · Analyze GC logs with GCViewer or gceasy · Understand modern collectors: G1, ZGC, Shenandoah, Parallel

Memory tools

In-depth guides in this category