Re: Diagnosing root cause of .NET application using nearly 500 MB
- From: Goran Sliskovic <gsliskov@xxxxxxxxx>
- Date: Mon, 17 Jul 2006 01:02:32 +0200
Matt Adamson wrote:
Hi William....
No, there are no specific objects here implementing IDisposable.
500 megs hasn't caused an issue however I would not have expected so much memory to be left claimed through the processing of the app. Clearly it never needs anywhere this amount of memory any of the time.
Ah, forgot to write in my previous post:
I used memprofiler from scitech few times and it was great help. Check it, there is free 14 day trial. You can create heap snapshots at different times and compere difference. If you have a leak, you'll find it fasts (allocation stack is also shown).
http://memprofiler.com/download.aspx
Regards,
Goran
.
- Follow-Ups:
- Re: Diagnosing root cause of .NET application using nearly 500 MB
- From: Chris Mullins
- Re: Diagnosing root cause of .NET application using nearly 500 MB
- References:
- Re: Diagnosing root cause of .NET application using nearly 500 MB memory
- From: Matt Adamson
- Re: Diagnosing root cause of .NET application using nearly 500 MB
- From: Matt Adamson
- Re: Diagnosing root cause of .NET application using nearly 500 MB memory
- Prev by Date: Re: Diagnosing root cause of .NET application using nearly 500 MB
- Next by Date: Re: Diagnosing root cause of .NET application using nearly 500 MB
- Previous by thread: Re: Diagnosing root cause of .NET application using nearly 500 MB
- Next by thread: Re: Diagnosing root cause of .NET application using nearly 500 MB
- Index(es):
Relevant Pages
|