Looking for Leaks

Use this forum for questions on how to use .NET Memory Profiler and how to analyse memory usage.
Post Reply

Looking for Leaks

Post by Keith » Mon Jun 06, 2005 8:44 pm

I have an application that is exporting data from multiple Exchange data stores (PST files) into a SQL database for analysis. As the application runs, it slowly allocates more and more memory.

I have installed your application and followed the tutorials to try and find the leak. When I filter for New or Removed Instances and switch to Dispose Info, only to very uninteresting classes remain.

What else should I be looking for?



Andreas Suurkuusk
Posts: 1029
Joined: Wed Mar 02, 2005 7:53 pm

Post by Andreas Suurkuusk » Tue Jun 07, 2005 9:27 pm

Does the profiler present increased memory usage of your application?

If the memory leak is caused by managed code, then you should be able to find one or more classes which have instances that is causing the leak. These classes do not necessarily have to be disposable, even though disposable classes can wrap unmanaged resources that might exaggerate the leak.

If the memory leak is not caused by managed code, the profiler will not be able present information about the leak (however, an unmanaged resources tracker will be included in future versions).
Best regards,

Andreas Suurkuusk
SciTech Software AB

Post Reply

Who is online

Users browsing this forum: No registered users and 20 guests