This you should know about memory problem Lollipop Android – Android Planet

This you should know about memory problem Lollipop Android – Android Planet

Android 5.0 and Android 5.1 Lollipop contend both with an annoying memory problem, making the RAM is filled slowly until it is full and crashes occur

<. p> Many thought that the original memory problem of Android 5.0 would be solved with the new version of Lollipop, but this is not the case. Android 5.1 introduces a new memory leak. Android Planet explains what is exactly wrong.

This is going wrong with the Lollipop memory problem

Lollipop Android 5.0 introduces a remarkable memory problem that is allegedly caused by bad code in ColorFade.java, is a key component for rendering images that is activated by switching on and off of the screen. The incorrect code apps are kept in memory even when you have the user exits the apps. After several hours of use, the free memory by about 50 percent have been reduced, with no more apps draaien.Dit ensures that the RAM memory becomes full at any given time, making Android apps suddenly shut to new memory free to make. In particular devices with 2GB or less of memory here.

last

The apps that are blocked by the memory problem, are mostly active apps running at the time. Think of Google Maps, Spotify and Netflix; apps that are running in the background. Also report many duped Android users that their launcher closes abruptly and reload. By the sudden closing apps that many users think Android Apps often simply crash. That is not the case, the memory problem Lollipop is in most cases responsible for sudden crashing apps.

The memory leak of Android 5.0 has now been resolved in Android 5.1, but in this version there is a new memory leak present.

This creates RAM problems with Android 5.1

Android 5.1 has the memory leak of Android 5.0 partially solved. Reportedly, the code of ColorFade.java improved, but Google is forgotten that not all Android apps that neat and works through the rules of Linux. Games that much memory questions are mostly the culprit, after closing the occupied RAM not return to the Android system. It is likely that the new leak is caused by changes that brings Android 5.1. Thus the new memory leak is not as large as that of Android 5.0, but again annoying

The problem occurs when a game like Farm Heroes Saga starts, and then closed the game by swiping from the multitask panel. Every time this happened, it occupied system memory is increased by approximately 100MB. This means that a portion of the ingested working memory is displaced by Farm Heroes Saga to the system. If your app ten times in one day start, system memory will soon about 1,3GB in. Just restart causes the increased system memory is reduced.

Google has now confirmed on the Issue Tracker Android that the problem of Android 5.1 is solved, but a release date is still unknown. Some think it is not necessarily the fault of Google, because the problem is caused by apps that are not optimally designed for Android. Others find that Google just to blame because they allow apps could cause this problem in Android.