OutOfMemoryException while populating MemoryStream: 256MB allocation on 16GB system

I’m running the following method on my development IIS server (from VS2010 IDE) on a 64-bit Windows 7 machine with 16GB of installed RAM:

public static MemoryStream copyStreamIntoMemoryStream(Stream stream)
    long uiLen = stream.Length;
    byte[] buff = new byte[0x8000];

    int nSz;
    MemoryStream ms = new MemoryStream();
        while ((nSz = stream.Read(buff, 0, buff.Length)) != 0)
            ms.Write(buff, 0, nSz);
        Debug.WriteLine("Alloc size=" + ms.Length);

    return ms;

and I get the System.OutOfMemoryException on this line:

ms.Write(buff, 0, nSz);

That is thrown when 268435456 bytes are allocated:

Alloc size=268435456

which is 0x10000000 or 256 MB. So I’m wondering if there’s some global setting that I need to set to make it work?

Here’s a screenshot of the configuration setting for the project:
enter image description here

Here is Solutions:

We have many solutions to this problem, But we recommend you to use the first solution because it is tested & true solution that will 100% work for you.

Solution 1

Short answer – dev server is 32bit process.

Long answer for “why just 256Mb?”

First of all, let’s understand how it works.

MemoryStream has internal byte[] buffer to keep all the data. It cannot predict exact size of this buffer, so it just initializes it with some initial value.

Position and Length properties don’t reflect actual buffer size – they are logical values to reflect how many bytes is written, and easily may be smaller than actual physical buffer size.

When this internal buffer can not fit all the data, it should be “re-sized”, but in real life it means creating new buffer twice as size as previous one, and then copying data from old buffer to new buffer.

So, if the length of your buffer is 256Mb, and you need new data to be written, this means that .Net need to find yet another 512Mb block of data – having all the rest in place, so heap should be at least 768Mb on the moment of memory allocation when you receive OutOfMemory.

Also please notice that by default no single object, including arrays, in .Net can take more than 2Gb in size.

Ok, so here is the sample piece which simulates what’s happening:

        byte[] buf = new byte[32768 - 10];

        for (; ; )
            long newSize = (long)buf.Length * 2;

            if (newSize > int.MaxValue)
                Console.WriteLine("Now we reach the max 2Gb per single object, stopping");

            var newbuf = new byte[newSize];
            Array.Copy(buf, newbuf, buf.Length);
            buf = newbuf;

If it built in x64/AnyCPU and runs from console – everything is ok.

If it built across x86 – it fails in console.

If you put it to say Page_Load, built in x64, and open from VS.Net web server – it fails.

If you do the same with IIS – everything is ok.

Hope this helps.

Solution 2

If you are using default VS development server you are running code in x86/32 bit process. If you are using full IIS – most likely in IIS particular AppPool is configured to runs in x86 (32 bit mode) and as result have very limited address space (2GB unless you have marked your application as Large Address Aware).

In case of IIS make sure you have configured app polls to run x64 (not sure what is default). Make sure your code is target is set to AnyCPU or x64.

For standalone C# applications – by default they are compiled with x86 or AnyCPU/Prefer x86 – change target platform to x64.

To get x64 support for IIS you can either install full IIS or install IIS Express 8.0 ( 7.5 that comes with Windows 7 is 32 bit only) from Download IIS 8.0 Express.

Side notes:

Note: Use and implement solution 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply