It is fairly normal to see consumption go up, as the GC is triggered by low
memory. It does not necessarily indicate a problem.
But, if there is COM interop, the memory usage may be indicative of a
problem. My suggestion would be to hammer the site with WAST or ACT (ships
with VS.NET Enterprise Architect) and see if the whole thing blows or if GC
handles the memory once it gets low. This will tell you if there is a leak.
With interop, leaks are often caused by not closing down objects explicitly.
--
Gregory A. Beamer
MPV; MCP: +I, SE, SD, DBA
************************************************** ********************
Think outside the box!
************************************************** ********************
"Geoff Pennington" <pe*********@stic2.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
The memory consumed by aspnet_wp.exe just keeps going up (as tracked in
Task Manager) until I restart it, so I must have a memory leak. If it makes a
difference, my app makes considerable use of Crystal Reports, and the
reports are exported to PDF format. Where should I look for the source of
my leaks? Also, what is the current "best practice" for deleting objects when
done with them? I have been lazy about doing that, thinking that the .Net
automatic garbage collection would take care of it for me.
Much obliged.
