Tagged articles
LeakCanary
11 articles · Page 1 of 1
Android 17 introduces MemoryLimiter, a system‑level app memory cap that silently kills processes exceeding device‑based limits, making unoptimized Bitmaps the biggest risk; the article explains the mechanism, detection methods, and five concrete Bitmap‑optimisation strategies plus new Android Studio tools to keep apps alive.
Android 17Android StudioBitmap optimization
0 likes · 20 min read

The NetEase Cloud Music Android team built a comprehensive memory‑monitoring system—combining LeakCanary and KOOM for leak detection, instrumented image loading for large‑bitmap tracking, periodic heap and thread metrics collection, and automated ticket generation—to identify, rank, and resolve leaks, oversized resources, and thread‑related OOM risks across development and production.
AndroidKOOMLeakCanary
0 likes · 15 min read

This article analyzes why Flutter apps suffer from high memory usage, identifies BuildContext and State as primary leak sources, and proposes a comprehensive, automated detection tool inspired by Android LeakCanary that accurately and efficiently finds memory leaks in production Flutter applications.
BuildContextFlutterLeakCanary
0 likes · 16 min read

This article explains why Android memory optimization is needed, introduces background concepts such as garbage collection and memory leaks, reviews common tools like Memory Profiler, MAT and LeakCanary, details image‑related memory reduction techniques, and presents the open‑source KOOM framework for online OOM detection and analysis.
AndroidKOOMLeakCanary
0 likes · 23 min read

This article provides a detailed technical analysis of LeakCanary 2.0, covering its Kotlin‑based integration, the new self‑implemented Hprof parser, detection workflow, core classes such as AppWatcher and ObjectWatcher, graph indexing, and the algorithm used to locate the shortest GC‑root leak path.
AndroidHeap AnalysisHprof
0 likes · 15 min read

This article examines why DialogFragment can cause memory leaks in Android apps, analyzes the role of HandlerThread messages and Looper processing, and presents several mitigation strategies including avoiding dismiss listeners, using weak references, and custom fragment implementations to safely release resources.
DialogFragmentLeakCanaryLooper
0 likes · 11 min read

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.
AndroidHeap AnalysisLeakCanary
0 likes · 17 min read

ResourceCanary, a Matrix sub‑module, automatically detects Activity memory leaks and redundant Bitmap objects in large‑scale Android apps by monitoring lifecycle callbacks, leveraging WeakReference queues, parsing Hprof dumps, and providing concise reference chains for fast debugging and performance optimization.
AndroidBitmapHprof
0 likes · 15 min read

This article explains the differences between stack and heap memory on Android devices, outlines typical memory problems such as high usage, leaks, and overflow, and demonstrates practical testing methods using the dumpsys meminfo command and the LeakCanary library with code examples.
AndroidHeapLeakCanary
0 likes · 5 min read

This article explains Android's memory allocation and reclamation mechanisms, enumerates common memory problems such as leaks, OOM, and bitmap handling, and demonstrates a comprehensive optimization case study on the JOOX music app that reduced average memory consumption by over 40 MB.
AndroidBitmapLeakCanary
0 likes · 24 min read

This article explains why Android apps encounter OutOfMemoryError, distinguishes memory leaks from heap overflow, and provides step‑by‑step guidance on using LeakCanary and the Eagle plugin for Eclipse to detect, compare, and fix memory leaks in Java applications.
AndroidEagleJava
0 likes · 5 min read
