Re: Winforms and memory usage
- From: bob clegg <cutbob_clegg@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Oct 2007 23:13:48 +1300
Hi,
Just a thought when profiling, allow sufficient time for the full
behaviour to be shown.
I went chasing a 'memory leak' where the Private bytes and Working Set
usage went up for several hours for no good reason I could see.
They finally levelled out then came down again. Then went up again
etc.
Took a couple of days of this wobbling behaviour before I accepted
that there was no leak.
Bob
On Fri, 12 Oct 2007 14:21:34 -0700, "Chris Mullins [MVP - C#]"
<cmullins@xxxxxxxxx> wrote:
Having spent far, far too much time at this, I would recommend two products.
over SOS:
- SciTech Memory Profiler is excellent. They have a 14 day free trial.
- RedGate ANTS Memory Profiler is also excellent. They also have a trial.
When I do seminars or mentoring on this, I always start with these products,
and only revert to Son of Strike and WinDbg as a very last resort. The
learning curve on SOS is brutal, and most devs won't ever get through it.
The learning curve for SciTech is about a day, and it's extremely powerfull.
Amazingly so.
The learning curve for ANTS is a few hours, but it's nowhere near as
powerfull as SciTech.
- Follow-Ups:
- Re: Winforms and memory usage
- From: Chris Alton [MSFT]
- Re: Winforms and memory usage
- References:
- Winforms and memory usage
- From: deerchao
- Re: Winforms and memory usage
- From: Chris Mullins [MVP - C#]
- Re: Winforms and memory usage
- From: Chris Mullins [MVP - C#]
- Re: Winforms and memory usage
- From: Chris Alton [MSFT]
- Re: Winforms and memory usage
- From: Chris Mullins [MVP - C#]
- Winforms and memory usage
- Prev by Date: RE: Thread monitor user input
- Next by Date: Timeout on "DataAdapter.Fill"
- Previous by thread: Re: Winforms and memory usage
- Next by thread: Re: Winforms and memory usage
- Index(es):
Relevant Pages
|