Android-5-1-AH-2

Android 5.1 Lollipop Memory Leak Issue Gets Internal Fix But Still Lacks Public Release

March 15, 2015 - Written By Justin Diaz

One of the bigger problems with the latest versions of Android software over these last few months since Android 5.0 Lollipop was released to the public, was the issue people were having with leaking memory. Normally Android’s memory woes are few and far between, but with Lollipop came about the memory leak bug which was more widespread than most would have hoped and the problem was bad enough that it quickly moved towards the top of the Google issue tracker. With the memory leak affecting more than a handful of users who had updated to Lollipop, people were seeing more constant app crashes and problems with re-launching apps because the memory would fill up but wouldn’t automatically clear out.

With the launch of Android 5.1 now upon us and the software going out to some Nexus devices, the memory leak issue would presumably begin to feel like an afterthought. However, In the last day or two it was discovered that Android 5.1 also had its own memory leak bug which was of course quickly reported to the people at Google via the issue tracker. While this is likely not what users were wanting to find in moving from a software version that already had problems with leaky memory, the good news is that Google seems to have internally fixed the issue.

The slight downside is that Google isn’t rolling things out just yet and they haven’t mentioned when they’ll begin pushing out the software fix for those users who are still experiencing the memory leak problems. Google states on the issue tracker that the problem is fixed internally, but they don’t have a timeframe for a public release, so users could end up having to wait another week or two, perhaps longer, before the software patch makes its way to devices being affected. Are you having an issue with leaking memory on Android Lollipop? If so what has it been affecting the most? If you’re curious to see the progress of this issue you can follow the issue tracker post at the source below. Although we will post an update when this problem gets fixed, Google will also likely update the issue tracker that the problem has been resolved and pushed out publicly.