Last week I began using Memory Profiler to analyze an application I've been working on for some time. There appears to be a memory problem that I cannot resolve. After using the Memory Profile (which is by far the best I've used thus far) I looked at the "Native memory" page.
On this page, under Private > Identified resources I found where the majority of my memory consumption is located: Kernel-VirtualMemory. Unfortunately, I have no idea what this actually means, nor and idea of how to reduce this memory consumption.
Does anyone have information related to the resource and what possible causes of high Kernel-VirtualMemory usage might be?
Thank you for the help.
The profiler tries to associate VirtualMemory with the "real" usage of the memory. For instance, if VirtualMemory is used for the managed heaps, the memory will be presented as "Managed heaps", rather than VirtualMemory.
In your case you have a large amount of memory that is only identified as VirtualMemory. How big is the memory usage? Have you tried to investigate the VirtualMemory instances in the "Types/Resources" view? You might get more information about the VirtualMemory by analysing the allocation call stacks.
SciTech Software AB
Once I removed the Bitmap.Save(string) invocation from the FOR loop the total memory usage dropped to under 20 MB.
I appreciate you taking the time to get back to me.
Users browsing this forum: No registered users and 14 guests