windowsprocessoperating-systemvirtual-address-spaceaddress-space

Why in address space's private regions so many zero bytes?

I'm examining process's address space under windows. When i see content of private regions, i wonder, because there are so many zero bytes (in some regions more than 95%). If more of private regions don't used while application is running, why they aren't only reserved or free?

Thanks to all.

Solution

  • Multiprocessing systems tend to initialize memory for security purposes. Usually, this is to zero. AIX at one time liked to initialize memory to 0xDEADBEAF.