We had the same discussion a while back; it turned out that this is a known bug in the GC. Arrays larger than 8MB are "sometimes" not collected correctly.
AFAIK there is no other workaround than splitting into smaller arrays. Maybe you could write a class with array behaviour and implement a sub-allocation strategy there? Well - that's no fun at all, but the only solution which comes to my mind :( I have been hoping that the CLR SP1 would fix this serious bug; but it's still there... Axel -----Original Message----- From: franklin gray [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 22. Mai 2002 21:28 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] 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? Thanks, Erick You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
