Re: Memory leak when using OleDb
- From: "Arild Bakken" <arildb_@xxxxxxxxxxx>
- Date: Fri, 5 May 2006 08:58:32 +0200
Well... the problem I have is in a huge application that creates a lot of
other objects and uses a lot of memory. And I can see that the memory does
sometimes "go down a bit", but that is only a couple of megabytes, and then
it startes growing again. The problem is that even after running for 6-8
hours the huge memory chunks are still not released.
Arild
"Göran Andersson" <guffa@xxxxxxxxx> wrote in message
news:%23mG0Ll8bGHA.3888@xxxxxxxxxxxxxxxxxxxxxxx
Probably not. That doesn't affect how the objects are disposed and
dereferenced.
Is it a real problem? The main reason that the code is using a lot of
memory is that you are creating a lot of connections and very few other
objects. In a real situation you would create a lot of other objects that
would cause garbage collections to occur more frequently.
Keith Patrick wrote:
Would putting those wrapper declarations into "using" blocks encourage
the GC to be a bit more aggressive with collection?
.
- Follow-Ups:
- Re: Memory leak when using OleDb
- From: Göran Andersson
- Re: Memory leak when using OleDb
- References:
- Memory leak when using OleDb
- From: Arild Bakken
- Re: Memory leak when using OleDb
- From: David Browne
- Re: Memory leak when using OleDb
- From: Keith Patrick
- Re: Memory leak when using OleDb
- From: Göran Andersson
- Memory leak when using OleDb
- Prev by Date: SmtpClient not accepting self-signed certificate
- Next by Date: Re: Modifiers of controls in UserControls
- Previous by thread: Re: Memory leak when using OleDb
- Next by thread: Re: Memory leak when using OleDb
- Index(es):
Relevant Pages
|