26 articles on Memory Leaks for Android performance
Showing 20 of 26 articles (Page 1 of 2)
Mahmut Yuce from Getir destroys the myth that declarative UI means no memory leaks. Compose apps leak differently, and these patterns are sneakier than the old View system bugs.
Taha Selim Aksakal from Teknasyon Engineering tracked down a memory leak that silently grew RAM usage from 160MB to critical levels over 12 hours—with zero traffic. The culprit? An unexpected interaction betwee...
Ricardo Marin from Grindr turned memory leak debugging from a 2-4 hour manual slog into a minutes-long automated process. The secret? Recognizing that memory leaks are pattern-matching problems, not creative on...
JioHotstar pushed their Android app from 99.5% to 99.8% crash-free rate by hunting down invisible memory killers. Here's how they did it.
Chamod Lakmal from PickMe reveals why November 1, 2025 marks Android's biggest performance shift since Android 5.0. Apps could launch 40% faster, but most developers aren't ready.
Brian Terczynski from Thumbtack tracked down a brutal Android OOM bug that was crashing apps at startup—and the culprit wasn't a memory leak. It was hiding in plain sight: their SQLite queries.
Dan Brown from Google Play just dropped a requirement that'll affect every Android app targeting Android 15+. Starting November 1st, 2025, your app must support 16 KB page sizes or risk breaking on next-gen dev...
Android Studio eating your RAM? You're not alone. A few strategic tweaks can reclaim gigabytes and slash build times by 20-50%.
Grab's configuration management SDK was crushing service performance with memory spikes and CPU throttling. 98% of services were loading 100x more data than they actually needed.
Lyft discovered memory leaks affecting only 1% of users—issues that would never show up in local testing. Here's how they built a production monitoring system to catch what profiling tools miss.
Grab's ML feature store went from 200ms to 2 second latency. The culprit? A single line of code in an async library.
Pinterest's API team just freed up 4.5GB of memory per host with a clever database swap. The result? Fewer servers, happier users, and a masterclass in optimization.
Dropbox's Android team was fighting OutOfMemoryError crashes. The culprit? Memory leaks hiding in activity lifecycles that traditional debugging couldn't catch.
Sid Rathi from Expedia Group debugged a production nightmare: KStream apps dying in an endless OOM loop. The culprit? A single unclosed iterator eating native memory.
Memory leaks are silent killers of Android app performance. They're hard to spot manually, but there's a tool that does the heavy lifting for you.
Ansgar Lin from Grindr Engineering found a single placeholder image consuming 8.3MB of memory at runtime. On devices with only 16-32MB Java heap, that's a recipe for constant crashes.
Facebook just open-sourced Hermes, a JavaScript engine built specifically for React Native on Android. This isn't just another optimization tweak. It's a ground-up rethink of how JS should run on mobile.
Ansgar Lin from Grindr Engineering discovered their app was crashing with OutOfMemoryErrors, and the culprit wasn't bad code. It was a tiny WebP image causing massive runtime memory allocation.
Marko Kevac from Bumble's Platform team benchmarked 6 associative array implementations to replace their aging Judy data structure. The winner? Not what you'd expect when memory matters.
Migrating from RxJava 1 to RxJava 2? The biggest gotcha isn't what you think—it's how you dispose of subscriptions.