I can make my application crash due to memory leak when repeating a known sequence of steps ~5 times. This behavoir does not occur however when my application is run under the profiler. I can repeat the same steps over and over and the memory is released. What is the profiler doing and how can I make my application do the same thing??
One possibility is that you have a deadlocked thread in your application, and the thread doesn't deadlock while running under the profiler. Deadlock scenarios are affected by the timing of the application, and if you deadlock a method running in the finalizer thread, then all finalizable objects will become uncollectible.
If you can provide more information about your application, and in what way you experience the memory leak, then I might be able to find out why the behaviour of your application is affected by the profiler.
SciTech Software AB
Users browsing this forum: No registered users and 14 guests