1. There is nothing inherently wrong in "leaking" a page which used to cache some word-readable file or belonged to a process you'd be able to ptrace anyway. 2

1. There is nothing inherently wrong in "leaking" a page which used to cache some word-readable file or belonged to a process you'd be able to ptrace anyway. 2. One could imagine this being configurable for embedded or HPC systems which don't care about security, though I'm not aware of people actually doing that. 3. The memory could equally well be overwritten with 0xdeadbeef and you have no control over that. 4. I once heard that Windows may sometimes fault-in nonzero pages if it runs out of pre-zeroed ones, but I couldn't locate this in MS docs so I'm not quite sure.