this too high, then we'll send out a memory pressure event every Z seconds (For example, we want BACKGROUND_PERCEIVABLE to stay alive.) If you set the highest priority class Y that you want to make an effort to keep alive. You should probably set this just above Y.KillUnderKB for Fire a memory pressure event when the system has less than Xmb of memory The threshold of the memory pressure event is configured in b2g/app/b2g.js, and the default value ( notifyLowMemUnderKB) is 14MB. When the memory pressure event was triggered, the services that are registered as memory pressure event observers will execute corresponding actions, such as eliminating or minimizing cache (temporary data of b2g). Pref('_PERCEIVABLE.OomScoreAdjust', 400) its OomScoreAdjust don't have a corresponding KillUnderKB.

okay, kernel will still kill processes with larger OomScoreAdjust first even The kernel can only accept 6 (OomScoreAdjust, KillUnderKB) pairs. When cache size and available memory are both lower than 4MB, the process, named b2g with oom_adj as 0 (MASTER) will be killed by LMKīy the way, LMK kills processes one-by-one, so we can be sure that memory leakage happens once b2g was killed by LMK.

When cache size and available memory are both lower than 8MB, the process with oom_adj as 8 (BACKGROUND_HOMESCREEN) will be killed by LMK.

When cache size and available memory are both lower than 20MB, the process with oom_adj as 10 (BACKGROUND) will be killed by LMK.

Let’s take the following table as an example: The thresholds are defined in b2g/app/b2g.js. When cache size or available memory is lower than a specified threshold, the system will trigger LMK to kill the process with oom_adj higher than 0 and to get some memory resources. LMK is a policy to obtain memory resources by killing processes in Android we integrate it into Firefox OS. There are three types of events which can get more memory when there is not enough memory on Firefox OS: Now, we would like to introduce the memory management and optimizations under the limited memory resources on Firefox OS. We know how to generate memory a footprint to debug memory leaks and to prevent abusing memory resources.

Firefox os x memory leak