Quantcast
Channel: GameDev.net
Viewing all articles
Browse latest Browse all 17825

Problem with PagedMemorySize64

$
0
0
I'm using C#, and trying to figure out how much memory a process is using within the paging file or how much of its memory within physical RAM can be moved to the paging file if necessary. Unless I'm mistaken (and I might be), the function PagedMemorySize64 is supposed to tell me how much is currently in the paging file, and PagedSystemMemorySize64 should tell me how much is in RAM but could be moved into the paging file at any time. If those assumptions are correct, then so far so good. However, even when "No paging file" is checked within my Virtual Memory properties window, these two functions both return positive numbers! Why would that be? Also, I opened the "Performance" tab on the Windows Task Manager, and in the section called "Kernel Memory (MB)" it says that "Paged" is a positive number (a pretty small number like in the hundreds, but I don't know if it's counting pages or bytes or what). Am I imagining things, or is my computer actually using a paging file even when I tell it not to, or alternatively, do those paged memory size 64 functions not work or just not do what I think they do?

Viewing all articles
Browse latest Browse all 17825

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>