Google Finally Plugs Marshmallow Memory Leak, Patch Coming In ‘Future Release'
Memory leaks continue to give some Android users headaches, especially those privileged to be running Android 6.0 Marshmallow. Well, the good news is Google and it's Android team seem to have discovered what's causing the memory leaks and have a fix in place. The bad news? You'll probably have to wait for Android N to benefit from the fix.
The memory leak in Marshmallow was brought to attention in November of last year on the Android Issue Tracker forum. At the time, it was noted that the "System UI" appears to just keep growing its footprint. An Android user provided screenshots showing it consuming more than 580MB and averaging 472MB, "which is more or less 4X the usage after a fresh boot." In other words, the longer an Android device affected by the issue was turned on, the more RAM it consumed, which could cause apps to crash and general instability.
Later that same month, an Android Project Member acknowledged that the memory leak was a defect in Marshmallow and that the issue had been passed on to the development team, along with a promise to update the status with more information as it became available. That's when things went fairly quiet on Google's end, until now.
"The development team has fixed the issue that you have reported and it will be available in a future build," a different Project Member recently stated.
The issue, which was assigned number 195104 and received nearly 500 stars from other users following its development, is now closed. However, since the patch is scheduled to arrive in a "future build," that could mean Android N.
The memory leak in Marshmallow was brought to attention in November of last year on the Android Issue Tracker forum. At the time, it was noted that the "System UI" appears to just keep growing its footprint. An Android user provided screenshots showing it consuming more than 580MB and averaging 472MB, "which is more or less 4X the usage after a fresh boot." In other words, the longer an Android device affected by the issue was turned on, the more RAM it consumed, which could cause apps to crash and general instability.
Later that same month, an Android Project Member acknowledged that the memory leak was a defect in Marshmallow and that the issue had been passed on to the development team, along with a promise to update the status with more information as it became available. That's when things went fairly quiet on Google's end, until now.
"The development team has fixed the issue that you have reported and it will be available in a future build," a different Project Member recently stated.
The issue, which was assigned number 195104 and received nearly 500 stars from other users following its development, is now closed. However, since the patch is scheduled to arrive in a "future build," that could mean Android N.
