A hello world .NET application on my machine uses 9KB of memory.
8.2KB is shared, 1.4KB is private.
According to the article most of that memory is because it's a DEBUG build and the debug CLR images are large.
8.2KB is shared, 1.4KB is private.
According to the article most of that memory is because it's a DEBUG build and the debug CLR images are large.
I think the issue is that the tool is showing you what is mapped into the address space of the process which may not use any memory. It could be mapped files or copy on write pages etc.
I think that I'll update the post with RELEASE mode screenshots, because having DEBUG ones just confuses things. Very few people (no-one?) will be running a DEBUG version of the CLR in real-world situations, so it's a bit confusing to use it.