Find what keeps
memory alive.
Turn a Java heap snapshot into an investigation. Explore retained memory, trace references, query objects, and review the code—without treating a suspect as a verdict.
VS Code and IntelliJ: Marketplace installation · Standalone: separate distribution
Analysis controls depend on the installed package, platform and version.
- Local .hprofCompleted, immutable snapshot
- Shared Rust engineQuick Scan or full graph analysis
- Staged resultsShallow first · retained when ready
Host adapters are alternatives. Memory is the default; optional Disk mode reuses verified structures. Terminal commands can run without a browser. Motion is illustrative, not measured timing. No analysis or network request runs here.
Start with evidence.
Keep the boundaries visible.
Understand the snapshot
Start with totals, then separate shallow storage from retained ownership.
02 / InvestigateFollow the evidence
Explore dominators, actual references, object fields, and paths to GC roots.
03 / AskQuery precisely
Use HeapQL filters, aggregates, joins, and supported subqueries.
04 / ReviewBridge to code
Resolve source through your host. AI suggestions remain proposals to inspect and test.
Local analysis.
Optional AI. Explicit limits.
The analysis engine reads your local dump. AI actions and telemetry have separate controls. Metadata can still be sensitive; approved AI fixes send the full source file.
One engine. Different environments.
VS Code, IntelliJ, terminal, browser, and MCP adapters reuse analysis—not every host capability. Setup and limitations are documented separately.
Explore the host guide →