0 views collected around this technical thread.
This article explains the various forms of Java OutOfMemoryError, their underlying causes such as heap exhaustion, GC overhead, metaspace limits, and native allocation failures, and provides practical solutions and code snippets to diagnose and resolve each scenario.
This guide explains why frequent garbage collection and heap memory overflow occur in Java applications, demonstrates how to reproduce the issue with a sample program, and walks through various techniques—including jmap histograms, heap dumps, VisualVM analysis, and remote JMX monitoring—to diagnose and resolve out‑of‑memory errors.
This article demonstrates how to use Eclipse Memory Analyzer (MAT) together with heap dump files to diagnose Java OutOfMemoryError issues, covering heap dump generation, histogram and dominator tree analysis, reference chain inspection, OQL queries, and a concrete Spring Boot example.
Learn how to export a live heap dump from a Java service, use JProfiler 9.x to open the .hprof file, identify large objects such as Zipkin's InMemoryReporterMetrics, and pinpoint memory leaks that can consume gigabytes of RAM.
This article explains how to avoid thread‑unsafe statistics collection by copying objects per thread, explores Java deep and shallow copying concepts, provides a concrete test program, and uses JConsole and heap dumps to verify the number of object instances created by each copying method.
This article explains Java heap dump files, detailing the concepts of shallow and retained heap, leading sets, dominator trees, and various types of garbage collection roots to help developers analyze memory usage and diagnose OutOfMemoryError issues.
A production Elasticsearch 5.3.2 cluster showed a persistent 80% heap usage due to a hidden memory leak caused by Log4j thread‑local objects retaining large bulk request data, and the article walks through the investigation, heap‑dump analysis, source‑code tracing, and a practical fix using a JVM flag.
This article introduces the Sieve Android memory analysis system, explains why existing tools like LeakCanary and MAT fall short, describes how heap dump files are parsed, GC Roots identified, dominator trees generated, retained sizes calculated, and reference chains constructed to help developers locate memory leaks and OOM causes.