The article explains common Android Out‑Of‑Memory scenarios, traditional analysis methods, and introduces the Shooter offline memory analysis system that parses hprof snapshots, builds dominator trees, computes shallow and retained sizes, and visualizes reference chains to help developers locate memory leaks and OOM causes.
This article introduces Sieve, an internal Android memory‑analysis platform that parses Hprof heap dumps, builds dominator trees, computes retained sizes, and constructs reference paths to help developers locate OOM‑causing leaks and optimize memory usage.
This article introduces Sieve, an internal Android memory analysis platform that parses Hprof files, builds dominator trees, calculates retained sizes, and visualizes reference chains to help developers identify OOM causes, while discussing the limitations of existing tools and implementation details.
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.
