memory management problem during debugging

  • Thread starter Thread starter Welman Jordan
  • Start date Start date
W

Welman Jordan

When I debug an asp.net application, which would consume
a considerable amount of memory, the application throws
"unhandled exception" and delivers a 500 error page to
the browser.

I find that the memory allocated by that application is
unable to reclaim. For example, I create a DataSet object,
the application quits with a exception during debugging,
the memory the DataSet consumes will not be returned to
the system, buried within the memory heap of aspnet_wp.exe.

What should I do to prevent this when debugging without
Vs.net installed on my machine?
 
Jordan,

Eventually .NET will reclaim the memory.

If you don't specifically reclaim memory yourself then the .NET garbage
collector reclaims it as necessary. There is no set time that the garbage
collector will fire so you can never be certain of exactly when the memory
will be reclaimed.

Here's an interesting article about the way the garbage collector works:

http://www.123aspx.com/redir.aspx?res=29698

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

Free code library at:
www.aboutfortunate.com

"Out of chaos comes order."
Nietzche
 
Back
Top