I understand the 2GB address space of 32 bit Windows. I gather you are saying that the "virtual" memory reported by the program as lacking is referring to addressable memory not used by the program up to the crash point. If so, I wouldsuppose that the error should have occurred when an attempt to allocate the new memory was made, not when the offending array was passed to a routine that would populate it. I admit that my knowledge of programming doesn't extend tohow the stack, the heap, etc. work.
In any case, is there any diagnostic code I can build into the program that will report at any point how much of the 2GB limit is in use? I would have guessed that the memory used by the program up to the extra 600 MB required by the array is only a few MB. Care has been taken to allocate/deallocate large arrays on the fly so as to avoid this kind of problem.
