Android Studio Profiler: Find Memory Growth
An app becomes sluggish after repeated navigation and may retain objects. This guide gives you a small, testable way to approach the issue before changing a live system.
A practical workflow
- Reproduce the sequence, capture a heap snapshot and compare retained instances.
- Trace references to the owner and fix lifecycle cleanup, then repeat the same sequence.
What to check
A rising graph alone is not proof of a leak; garbage collection and caches affect memory patterns. Compare the result with the original problem and record what changed. If a measurement or test does not support the change, revisit the assumption rather than adding more complexity.
Keep the experiment small enough to reverse. Document the starting state, the change and the result so another person can repeat the process. Product menus and versions can change, so check the current documentation for your environment.
Official reference: Read the documentation.