John,
It is hard to say anything without some data. As just a guess, you might
have missing Disposes(), double/triple caching, missing shared state
cleanup..
I think it could be anything. To get some facts, I would advise you to make
a dump of the web application when it reaches the 1.2Gb and then use WinDBG
to check what it has eaten.
With WindDBG and SOS you can get all the heap statistics, objects allocated
and all the other necessary things to understand what is going on.
It is not hard at all. Actually it is much better than using profiler.
Here some good articles:
http://blogs.msdn.com/johan/archive/...mory-dump.aspx http://blogs.msdn.com/johan/archive/...bg-part-i.aspx http://blogs.msdn.com/johan/archive/...g-part-ii.aspx http://blogs.msdn.com/johan/archive/...hoot-this.aspx
LT
"John Sheppard" <sp**@nospam.comha scritto nel messaggio
news:fn*********@news2.newsguy.com...
Hello,
I have been trying to track down a problem.
The symptoms are as follows
- My application takes up 1.2gb of memory (when looking in windows task
manager)
- It runs very slowly
To fix the problem I do the following;
- Delete all files out of my bin and obj directory and compile
- Its runs lightning fast and only consumes 370mb of memory (when lookin
in windows task manager)
When I deploy the application or do a random amount of builds the symptoms
return.
Does anyone have any thoughts on why this might be occuring?
Im trying to use the CLR profiler, but it takes a bit of
learning...hopefully this well help...
Thank you
John Sheppard
