2017 DevFestMN Emmett Wilson
summary
An app that gets killed and recreated leaves lost in‑memory models and flaky UI leading to crashes the claim is that this is common and testable. Methods demonstrated include non deterministic RAM pressure from heavy apps, the Samsung font trick, toggling no background processes in developer options, and a tiny open source utility called app terminator that kills a target process and reliably reproduces recreation in seconds. Practical gotchas include handling persistence, avoiding transaction too large on Nougat, and choosing flat JSON versus SQLite tradeoffs.
AI-written summary · about
chapters (5)
- 0:00Android zombies introduction
- 1:49Defining zombie apps
- 6:06Testing process death
- 15:17Recovery strategies
- 25:30Q&A
related talks
28mAndroid Zombies: How to Not Get Bit
41mEmbracing the Chaos: Investigating Production Madness
49mKeynote: Android Development
34mKeynote: Comedy Talk - Better Android Development (BAD)
45mThe Immortal App
42mWorking Effectively with (Android) Legacy Code
37mHow to survive on Android and don't get killed
08h 39mLivestream | Day 2, theater 2
