9

we need a tool to detect easily memory leaks in an ASP.NET Application. We have an application, which consumes lot of memory.

Thanks

ChaosSpeeder
  • 3,468
  • 5
  • 30
  • 38

9 Answers9

4

I have published a new article on the subject on MSDN. It contains a list of tools.

Fabrice
  • 3,094
  • 3
  • 28
  • 31
  • I think I know the screens used in the custom tools section. We worked on the same product :) – pix Oct 14 '16 at 09:25
4

Using WinDbg is not as easy as using dotTrace but it can help you to discover lots of oddities in your application. Other than that you can find invaluable information about debugging ASP.Net applications on Tess Ferrandez's blog.

idursun
  • 6,261
  • 1
  • 37
  • 51
4

Rob Mariani wrote a nice article on Tracking down managed memory leaks which helped me track down the dangling references in a desktop application.

Moses Machua
  • 11,245
  • 3
  • 36
  • 50
Todd Smith
  • 17,084
  • 11
  • 59
  • 78
2

Well, "easily" is the trick... however dotTRACE might be worth a look.

Marc Gravell
  • 1,026,079
  • 266
  • 2,566
  • 2,900
2

check out Microsoft's FxCop which also analyzes performance issues, etc.

Spikolynn
  • 4,067
  • 2
  • 37
  • 44
1

.Net Memory Profiler. Used the trial version once. It was helpful, but I don't need it often enough to warrant buying one.

The thing I found was to ALWAYS make sure you dispose of any resources, particularly in DirectoryServices, that implement IDisposable.

tvanfosson
  • 524,688
  • 99
  • 697
  • 795
  • 1
    Actually, don't try to dispose disposable static resources such as Brushes.Black if you intend to use them again :) Learned that the hard way... – Spikolynn Jan 23 '09 at 17:38
0

I found this one quite useful too: http://www.codeproject.com/Articles/19490/Memory-Leak-Detection-in-NET

Summary of the interesting points:

  1. Use Perfmon to monitor .Net CLR Locks/# of current logic threads to see if you are creating threads but not destroying them.
  2. Use Perfmon to compare .Net CLR/# Bytes vs. Process/Private bytes to see if it is managed or unmanaged memory that is leaking
  3. Assuming its managed memory that is leaking, using windbg/sos.dll to track down the references
steve cook
  • 3,116
  • 3
  • 30
  • 51
0

I read about Ants Profiler. Good luck.

tobsen
  • 5,328
  • 3
  • 34
  • 51
0

Read Tess at If broken it is, fix it you should. It should get you on the right path.

idstam
  • 2,848
  • 1
  • 21
  • 30