Loading page...
Q&A
Q&ACompare post-GC live-set size and object retention paths over time.
High allocation can cause frequent collections while post-GC occupancy remains broadly stable. A leak tends to retain objects that should have become unreachable, so compare heap dumps and dominator paths across time. Check allocation rate, live set, GC logs, and process/container memory together before changing heap settings.
Q&A
Q&ACorrelate GC logs, allocation rate, live-set size, pause phases, and user latency before tuning.
Enable and inspect unified GC logs for pause duration, cause, heap before/after, promotion, and allocation behavior. Correlate with request latency and container memory. A large live set, allocation bursts, humongous objects, or memory pressure can imply different fixes; tune collector flags only after identifying which resource or workload pattern drives the pauses.
Q&A
Q&AIt is no longer strongly reachable from GC roots, though collection timing is not guaranteed.
An object becomes eligible when no strong-reference path leads to it from roots such as live thread stacks, static fields, or JNI references. Eligibility does not guarantee immediate collection or finalization. To diagnose retention, inspect heap dumps and dominator paths; do not rely on System.gc() as a fix.
java
18 minA production field guide to GC choice, thread-pool saturation, Spring lifecycle traps, AOP boundaries, and blocking work in reactive services.