Is Private Bytes >> Working Set normal?
- by Jacob
OK, this may sound weird, but here goes.
There are 2 computers, A (Pentium D) and B (Quad Core) with almost the same amount of RAM running Windows XP.
If I run the same code on both computers, the allocated private bytes in A never goes down resulting in a crash later on. In B it looks like the private bytes is constantly deallocated and everything looks fine.
In both computers, the working set is deallocated and allocated similarly.
Could this be an issue with manifests or DLLs (system)? I'm clueless.
Also, I compiled the executable on A and ran it on B and it worked.
Note:
I observed the utilized memory with Process Explorer.
Question:
During execution (where we have several allocations and deallocations) is it normal for the number of private bytes to be much bigger (1.5 GB vs 70 MB) than the working set?