[delayed]
You have described the current state of Android development if you want your app to stay alive and be useful without its GUI in the foreground. It is an insidious process that has essentially broken the OS more with each release, and broken apps that were mindful of battery usage but didn't pull the correct magical levers.
"All means are fair except solving the problem"
I think what they are saying is if OOM was going to kill the process anyways, it can defer this a bit and only fault on read or write on the rarely used memory.
So don’t change the OOM descision making, just the action taken.
I think the person below makes a good point though, that this encourages or permits buggy code.
OOM triggers when memory pressure is critical; it's not practical to further defer addressing it at that point.
Huh? Defer addressing? The memory would be reclaimed in this scenario, it is entirely “practical” in that sense.
Defer /addressing/fixing/solving/ the problem.
If the oomkiller is running, it's too late to wait and see: some process or kernel thread needs memory that the kernel can't currently provide
Sure, they will get restarted, but not great.