English
Skip to content
100% client-side · Free · No sign-up
See exactly what your garbage collector is doing
Drop in a JVM GC log and get an instant report — throughput, pauses, memory-leak signals and tuning advice. Parsed entirely in your browser; your logs never leave your machine.
Leak signal detected
ZGC sub-ms pauses
Throughput
99.3%
Max Pause
284.5 ms
Full GC
1
Alloc Rate
153 MB/s
System.gc() · consider -XX:+DisableExplicitGCEvery major collector supported
From legacy deployments to the latest JDKs — unified logging and classic formats alike.
SerialParallelParNew + CMSG1ZGCShenandoahJava 1.2 – 25
Everything the report tells you
Not just charts — every number is computed from your log and traceable in the event table.
15
Tuning recommendation rules
6
Garbage collectors recognized
1.2–25
Supported Java versions
0
Log uploads — ever
Built for production debugging
The checks you actually need at 3 AM, one click away.
Instant, Private Analysis
Results in seconds. Parsing happens locally in your browser — nothing is uploaded, ever.
Memory-Leak Detection
Linear regression over the after-GC footprint catches a steadily growing old generation before it takes the service down.
Pause & Throughput Metrics
Throughput, average / P99 / max pauses, allocation rate and the full timeline of every collection.
Actionable Advice
Concrete JVM flags — from -XX:+DisableExplicitGC to right-sizing the heap — each tied to what your log shows.
Traceable Numbers
Every metric maps to the parsed event table, so you can cross-check against your own application logs.
English & 简体中文
Site and reports fully bilingual. Switch anytime from the language menu.
Three steps to insight
Safe to keep enabled in production — logging overhead is typically under 3%.
1
Enable GC logging
Java 9+: -Xlog:gc*:file=gc.log
Java 8: -XX:+PrintGCDetails -Xloggc:gc.log
2
Drop in the log
Drag the file into the analyzer — parsing happens right in your browser, no account required.
3
Act & verify
Follow the recommendations: fix leaks, right-size the heap, cut pauses — then re-analyze to confirm.
Why run logs through EasyGC?
The difference is architectural: there is no server to trust.
Traditional online analyzers
- Your GC log is uploaded to a third-party cloud
- Sign-ups, quotas and processing queues
- Black-box rules you cannot inspect
EasyGC
Local-first analysis
- Parsed in your browser — the log never leaves the machine
- No sign-up, no quota; works offline after the page loads
- Deterministic rules — every metric traceable to your log
- Self-hostable static site for intranets
Ready to decode your first GC log?
Free, no sign-up, no upload. See a full report in ten seconds.
Analyze now — try the live sample