square/leakcanary
Leakcanary
LeakCanary is a diagnostic tool designed to identify memory leaks by monitoring object lifecycles and analyzing heap snapshots. It automatically detects objects that fail to be garbage collected after their expected lifespan, providing developers with actionable insights to prevent performance degradation and application crashes.
The project distinguishes itself by offloading memory-intensive heap parsing to a separate background process, which minimizes performance impact on the main application during runtime. It includes sophisticated deobfuscation capabilities that map obfuscated stack traces back to original source code, and it supports granular control through reference filtering and custom inspection logic to suppress known false positives.
Beyond core detection, the tool offers comprehensive configuration options for managing analysis thresholds, build-specific behaviors, and environment-specific monitoring. It provides both deep heap analysis for development environments and lightweight instance tracking for production builds, ensuring memory health can be monitored across the entire application lifecycle.
Features
- Memory Leak Detection - Provides automated detection and filtering of memory leaks to prevent false positives during heap analysis.
- Debugging and Inspection - Memory leak detection library.
- Developer Utilities - Automated detection of memory leaks during development.
- Instrumente de dezvoltare - Detect and identify memory leaks during development.
- JVM Profiling Tools - Memory leak detection library for Android and Java.
- Static Analysis - Offloads memory-intensive heap parsing to a separate background process to prevent performance degradation.
- Performance Analysis - Tracks retained object counts to detect potential memory pressure issues during application execution.
- Reverse Engineering Tools - Automatically maps obfuscated stack traces back to original source names to simplify debugging.
- Execution Tracers - LeakCanary automatically maps obfuscated code back to original source names by applying a plugin that translates stack traces during development builds.
