The IsLowMemory predicate allows a piece of code test to see if we are in a low memory situation. We only do this sort of test in two major places:
1) allocation of image data
2) during js callbacks
Testing for low memory requires us to read proc files, or acquire a kernal lock (like when we have to call into GlobalMemoryStatus on windows). On Windows CE we disabled this check all together because of the cost.
(1) doesn't really matter that much in terms of perf, but (2) really does.
In addition, some memory allocators do reservations and commit on write. In this case, the test would not actually do what you wanted.
So, I think we should move away from using IsLowMemory. Instead, we should continue broadcasting memory-pressure notifications when we can and if the OS has such a feature. For example, on osso, we get a notification that our process is running low on memory. We can also detect this on Android.
If this is agreeable, we can remove the IsLowMemory() callers, make the call return false, and add documentation about deprecating this method.
Created attachment 470824 [details] [diff] [review]
Documented this change:
And mentioned it here as well:
and of course on Fx4 for developers.