Re: Memory leak when using Response.Write()
- From: Göran Andersson <guffa@xxxxxxxxx>
- Date: Sun, 02 Jul 2006 14:13:18 +0200
When you remove the reference to the dataset, it won't be collected immediately. It will be collected when the garbage collector is run, and that only happens when the memory is needed, or when the garbage collector thinks that it's convenient to do a collection.
It's normal for the memory usage to increase while an application runs. If your application uses and releases a lot of objects, you would observe a sawtooth like curve where the memory usage increases to a certain point until a garbage collection occurs and frees up a ot of memory at once.
Piotrek wrote:
Thanks for your answers..
So if it is not a problem with frames, then I have no idea, what it can
be.
What more I noticed is that there are datasets (datacolumns,
dataviews), which are not collected by GC. I store results of search in
Session as datasets, but after a while I set them to null, so they
should be collected.
One more thing I do not understand is why usage of memory increases
after executing the code I posted earlier and before PageLoad method is
called.
I know that it is hard for you to answer that questions, but maybe you
know something, which could help me?
Piotrek.
- Follow-Ups:
- Re: Memory leak when using Response.Write()
- From: Piotrek
- Re: Memory leak when using Response.Write()
- References:
- Memory leak when using Response.Write()
- From: Piotrek
- Re: Memory leak when using Response.Write()
- From: Göran Andersson
- Re: Memory leak when using Response.Write()
- From: Mark Rae
- Re: Memory leak when using Response.Write()
- From: Göran Andersson
- Re: Memory leak when using Response.Write()
- From: Piotrek
- Memory leak when using Response.Write()
- Prev by Date: Re: Invalid URI: There is an invalid sequence in the string. Error!!
- Next by Date: Still Need desperate help to start with ASP NET - simplified problems - HELP!!
- Previous by thread: Re: Memory leak when using Response.Write()
- Next by thread: Re: Memory leak when using Response.Write()
- Index(es):
Relevant Pages
|