Is this any single object using 8mb? or is it the root object and all children using 8mb?
I am pretty sure a Foo class that is 8mb will leak based on the what I have read so far, but what about an ArrayList containing 10 of objects that are 1mb or some other combination that equals or exceeds 8mb (except 1 x 8mb). What about for DataSets, DataTables, HashTables, etc? I assume intrinsic arrays would depend on the type of array? So that an array of reference types that was 10 entries of 1mb each would not have this problem, but an array of value types that added up 8mb would? I am also assuming that if the array of 2 million reference types would be large enough to exceed the 8mb on its own (assuming 4 bytes or so per entry)? David -----Original Message----- From: Bryan Batchelder [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 23, 2002 8:33 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Large object memory leak - workaround? I don't know if it is related, but there is a bug in ASP.NET when reading (via HTTP upload) large files (above 8 MB). It leaks bad. I am with Thomas on this one, without the autorecycling, ASP.NET would not be usuable for many of the projects I have completed with it. --b Bryan Batchelder eBusiness Consultant ConnectWise, Inc. 813-935-7100 x 425 > -----Original Message----- > From: Thomas Tomiczek [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 23, 2002 4:28 AM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] Large object memory leak - workaround? > > > 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. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business units of CREDIT SUISSE FIRST BOSTON reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. Unless otherwise stated, any pricing information given in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
