In the Android community, Lollipop 5.0 is known for a lot of things. Unfortunately, among those things is a pretty severe memory leak that has plagued users with app crashes and launcher redraws, as device memory filled and failed to clear.

When Android 5.1 was announced, many hoped the issue would finally be resolved. After all, Google did mark the memory leak (which climbed to the 34th highest position in the issue tracker's history) as "future release" back in December.

As it turns out though, Lollipop 5.1 is not without its own memory leak, at least for some users over at the issue tracker. But Google has some good news and some bad news. The good news is that the 5.1 memory leak has been "fixed internally." The bad news? "We do not currently have a timeline for public release."

Project Member #35 [email protected]
This has been fixed internally. We do not currently have a timeline for public release.

Status: FutureRelease
Labels: Restrict-AddIssueComment-Commit

The status change appeared 39 hours ago (at the time of writing) on an issue created March 12th, which you can check out for yourself below. Here's hoping the fix doesn't take too long to appear publicly, whatever the version number.

  • Thanks:
  • Vinoth,
  • Mehdi,
  • Ravi,
  • Sam,
  • Rodrigo,
  • jlmcr87,
  • Dylan