4 ms·
That link says: "Allocates memory charges (from the overall size of memory and the paging files on disk) for the specified reserved memory pages." It does coun
by MichaelGG 13y ago
That link says:
"Allocates memory charges (from the overall size of memory and the paging files on disk) for the specified reserved memory pages."
It does count against the total memory allowed. My laptop has 8GB of RAM and 1GB page, giving me a 9GB overall commit limit. If I spawn a process that eats up 1GB at a time, even Task Manager can clearly show me going up and hitting 8/9GB, then I'll get OOM in my process.
Windows won't commit memory that a process can't use. You can't overcommit, although you might end up in the pagefile. Without the odd concept of fork, you don't end up with processes having huge "committed" address spaces that aren't ever going to be used.
The note about physical pages is just saying it's not mapping it, not that it's not guaranteeing it.
- kyberias 13y agoRight. I stand corrected.