It doesn't matter what the objects are, this is a bug which affects ALL objects over 8MB.
Making them disposable won't make any difference, since the dispose pattern is used to free resources *other than* memory allocated in the managed heap. Besides which, the GC knows nothing about IDisposable. A fix has been promised... Sorry Erick, I don't know of any workaround, other than the obvious ;) G. -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of franklin gray Sent: 22 May 2002 20:28 To: [EMAIL PROTECTED] Subject: Re: Large object memory leak - workaround? Are you referring to custom objects or all object like a XmlDocument? This is just a guess, but if it's a custom object, code and execute a dispose method. This might let the GC know that you ar e done with it. -----Original Message----- From: Erick Thompson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 2:10 PM To: [EMAIL PROTECTED] Subject: [DOTNET] Large object memory leak - workaround? I've run across the large object memory leak/bug, where objects larger then 8 megs aren't getting freed. However, I can't find a workaround (aside from only using smaller objects :) Does anyone know how to work around this issue? You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
