Objects that large are allocated from the Large Object heap and placed directly into generation 2 so they are not collected very often. Are you sure you're leaking? how can you tell. I'd suggest using the perform counters - ".NET CLR Memory" if you haven't already. Watch the # Gen 2 collections and the Large Object Heap Size counter.
Good luck Jim > -----Original Message----- > From: Erick Thompson [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 22, 2002 3: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.
