You are currently offline, waiting for your internet to reconnect

BUG: Passing large quantities of data in .NET Remoting calls causes an unexpected exception to occur

This article was previously published under Q322975
This article has been archived. It is offered "as is" and will no longer be updated.
You can use .NET Remoting to allow instances of any type that can be serialized to be passed as method parameters between the client and the server applications. However, if the type instance that is passed is very large (tens of megabytes), the Remoting client consumes large amounts of virtual memory and then generates unexpected exceptions. The exceptions can be either OutOfMemoryException exception or SocketException exception. The commit charge as seen in Task Manager is also very high.
This is because of a bug in the .NET Remoting system.
To work around this problem, pass smaller amounts of data with each remoted call. You can also pass a Stream object as a method parameter. Stream objects inherit MarshalByRefObject. You can use the Stream object to retrieve data in smaller chunks.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
When the class below is hosted in a Remoting host, and the method is called by a Remoting client, the problem occurs. The following code fragment demonstrates the problem:

	public class MBRClass : MarshalByRefObject	{		public byte[] GetBigByteArray ()		{			byte[] byteArray = new byte[60000000] ;			return byteArray ;		}	}				

Article ID: 322975 - Last Review: 02/27/2014 18:42:23 - Revision: 4.4

Microsoft .NET Framework 1.0, Microsoft .NET Framework 1.0 Service Pack 1, Microsoft .NET Framework 1.0 Service Pack 2, Microsoft .NET Framework 1.1, Microsoft .NET Framework 1.1 Service Pack 1

  • kbnosurvey kbarchive kbbug kbremoting KB322975