Well, there is a 2GB limit on the size of a process in Win32. You can
up this slightly using the /3GB switch
http://blogs.msdn.com/oldnewthing/ar...13/214117.aspx
However, another big issue is what you memory looks like inside the
process - i.e. are you trying to allocate huge arrays? If so,
fragmentation will be a major issue, that could trigger an
OutOfMemoryException, presumably crashing your app.
Another consideration is: are you using your memory effectively? Hard
to tell without a /lot/ of info, though.
You could switch to Win64, but note that this changes the equation;
each reference has a larger footprint. If you have a huge array of
structs this is probably fine. If you have a huge array of objects (or
just a lot of references generally) your memory consumption will jump
yet further. But the process will have more space, so it is a double-
edged sword.
Marc