Home/ Questions/Q 283567
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T05:23:04+00:00

As I understand it there’s a 2 GB limit on single instances in .NET.

  • 0

As I understand it there’s a 2 GB limit on single instances in .NET. I haven’t paid a lot of attention to that since I have mainly worked on 32 bit OS so far. On 32 but it is more or less an artificial limitation anyway. However, I was quite surprised to learn that this limitation also applies on 64 bit .NET.

Since collections such as List<T> use an array to store items, that means that a .NET application running on 32 bit will be able to hold twice as many reference type items in a list compared to the same application running on 64 bit. That is quite surprising imo.

Does anyone know if this limitation is addressed in CLR 4.0 (I don’t have a 4.0 installation at hand at the moment).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s worse than that – you’re process space, when you’re working in .NET in 32bit is much smaller than the theoretical limit. In 32bit .NET apps, my experience is that you’ll always tend to start getting out of memory errors somewhere around 1.2-1.4gb of memory usage (some people say they can get to 1.6… but I’ve never seen that). Of course, this isn’t a problem on 64bit systems.

    That being said, a single 2GB array of reference types, even on 64bit systems, is a huge amount of objects. Even with 8 byte references, you have the ability to allocate an array of 268,435,456 object references – each of which can be very large (up to 2GB, more if they’re using nested objects). That’s more memory than would ever really be required by most applications.

    One of the members of the CLR team blogged about this, with some options for ways to work around these limitations. On a 64bit system, doing something like his BigArray<T> would be a viable solution to allocate any number of objects into an array – much more than the 2gb single object limit. P/Invoke can allow you to allocate larger arrays as well.

    Edit: I should have mentioned this, as well – I do not believe this behavior has changed at all for .NET 4. The behavior has been unchanged since the beginning of .NET.

    Edit: .NET 4.5 will now have the option in x64 to explicitly allow objects to be larger than 2gb by setting gcAllowVeryLargeObjects in the app.config.

    • 0