I sincerely hope MS listens to this and puts out a service pack on this soon :-) Frankly, if ASP.NET would not recycle processes some of the things I have done for customers would probably be unusable due to the large object issue :-)
Regards Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) -----Original Message----- From: Graeme Foster [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 23. Mai 2002 10:23 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Large object memory leak - workaround? I didn't mean to sound so sure :) But even if it's just arrays (and it'd be hard to create such big objects without using arrays) then MemoryStream should be affected. :( G. -- Graeme Foster ([EMAIL PROTECTED]) Principal Software Engineer Aston Broadcast Systems Ltd. (http://www.aston.tv) Disclaimer: I really don't have a clue what I'm on about. -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Zane Thomas Sent: 23 May 2002 01:43 To: [EMAIL PROTECTED] Subject: Re: Large object memory leak - workaround? > It doesn't matter what the objects are, this is a bug which affects ALL > objects over 8MB. Seems that would be a problem for anyone using a large memory stream. ************************************************************************ ***** The contents of this email and any attachments are confidential. It is intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to any one or make copies. ** eSafe scanned this email for viruses, vandals and malicious content ** ************************************************************************ ***** 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.
