This behaviour is not experienced on v2.6.
Thank you for the information. This is something we have not tested, but we will make sure that we look into this before making the next release of .NET Memory Profiler 3.0.
What settings were you using when this problem occured? Was the unmanaged resources tracker enabled?
SciTech Software AB
Users browsing this forum: Bing [Bot], Google [Bot] and 8 guests