i have a problem running my testcases. for each testcase my application is loading a document, processes it and finally discards of the document. this happens ~400 times in a row. while the application is running, the gc heap doesn't seem to have a leak - the gc heap size stays essentially the same for each processed document. however, the working set size and the memory load is increasing all the time. there is an image with some simple stats here: http://muenchen.die.de/memory.gif (the red line is the gc heap, green is working set and blue is memoryLoad.)
i have already verified that there are no leaks in the gc heap using memory profiler. i've also looked at the "native memory" by comparing a snapshot that was taken before the testrun and afterwards - however, there is only a diffenrence of ~ 20 k. so it looks like there isn't a "big" leak in native memory.
(this is a native c++/cli/managed application c#).
however, i still get OutOfMemoryExceptions at some point during the testrun - by looking at the graph it's obvious there must be some kind of leak. however, i haven't got the faintest where to look for whats causing the increase in memory load etc.
Can you provide some additional numbers? How big is your working set compared to the amount of memory presented by the native memory view?
Have you looked at the total memory usage including profiler data? If you have a test that is creating a lot of dynamic assemblies, the amount of profiler data will increase (profiler information about classes etc. never gets unloaded).
SciTech Software AB
Users browsing this forum: Google [Bot] and 12 guests