This could be a generalization of the OOM killer. When memory is tight, some unlucky process is chosen and any pages it hasn't used recently are marked as volatile. It keeps running but if it tries to access one of those pages then boom! This might be a bit better than just killing it immediately. I would guess that many user-space applications leak memory, in the sense that they allocate pages, use them for a bit and then never touch them again.