Within the Android community, Lollipop 5. is famous for several things. Regrettably, among individuals things is a nice severe memory leak which has plagued users with application crashes and launcher redraws, as device memory filled and unsuccessful to obvious.

When Android 5.1 was announced, many wished the problem would finally be resolved. In the end, Google did mark the memory leak (which rose towards the 34th greatest position within the issue tracker’s history) as “future release” in December.

Actually though, Lollipop 5.1 isn’t without its very own memory leak, a minimum of for many users at the problem tracker. But Google has what’s promising and a few not so good news. The good thing is the 5.1 memory leak continues to be “fixed internally.” Unhealthy news? “We don’t presently possess a timeline for public release.”

Project Member #35 al…@android.com

It has been fixed internally. We don’t presently possess a timeline for public release.

Status: FutureRelease

Labels: Restrict-AddIssueComment-Commit

The status change made an appearance 39 hrs ago (during the time of writing) with an issue produced March twelfth, which you should check out on your own below. Here’s wishing the fix does not take too lengthy to look openly, regardless of the version number.