Memory Dumps: Going beyond the memory leak
summary
Claims that a new compact format and tools let developers extract concrete debugging data from Android memory dumps: a 210 MB HPROF becomes a 3.8 MB BMD (about 1.8% of the original) and compresses to 1–2MB for upload. Tools reconstruct view hierarchies and extract intents, sockets and bitmaps, convert on device to avoid heavy transfers, and ship as open source for integration. Demos show recovered UI and a background converter that works well enough to be practical.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:14Inside the Memory Dump
- 4:07Current use cases
- 9:32View Hierarchies
- 10:57Outlines
- 13:31Colors
- 14:14Images
- 20:11Limitations of HPROF
- 24:30Better Memory Dumps
- 25:56Introducing BMD
- 30:47Practical Applications
- 33:22How to use it!
related talks
20mMaking the memory dump a powerful development tool
07mAndroid memory tools and best practices
47mTackling Memory Issues on the Instagram Android App
36mAndroid memory and games
40m640K ought to be enough for anyone
53mMemory on Android, Leaks and OOM
24mUnveiling the Unseen Threat: Demystifying Memory Leaks in Android
49mTrash Talk