Re: Windows array allocation problem

Louis Krupp wrote:

You're not really allocating memory; you're allocating an address range. If the available virtual addresses aren't in one contiguous chunk, you won't be able to allocate them all at once.

That's disappointing news. It means that it could be possible for there to be, say, 1.5 GB of available virtual memory, yet it be impossible to allocate an array of 100 MB. How could you tell in advance (without doing a loop with a STAT parameter) how much you could allocate?

I'm surprised that the virtual memory is so badly fragmented early in the program, if that's the cause of what I'm seeing. No deallocation has taken place by that point, so the cause of the fragmentation is a mystery. Do you have any idea what the cause could be?

Roy Lewallen
.

Relevant Pages

  • Re: memory leak
    ... MSFT have already said that they will fix this problem, ... What is your definition of "video RAM"? ... You could try to allocate and have it throw if you're out of virtual memory. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Windows array allocation problem
    ... I'm getting an "insufficient virtual memory" error when trying to allocate an array to a size which is about 385 MB less than the amount of available virtual memory. ...
    (comp.lang.fortran)
  • Re: Windows array allocation problem
    ... allocate an array to a size which is about 385 MB less than the amount of available virtual memory. ... In both cases a call to Windows API function GlobalMemoryStatus or GlobalMemoryStatusEx immediately before the ALLOCATE statement returns a value of available virtual memory of 2,118,221,824 bytes. ... So I'm getting an "insufficient virtual memory" failure when trying to allocate the array to a size which is 384.665 MB less than the amount of reported available virtual memory. ...
    (comp.lang.fortran)
  • Re: Windows array allocation problem
    ... allocate an array to a size which is about 385 MB less than the amount of available virtual memory. ... In both cases a call to Windows API function GlobalMemoryStatus or GlobalMemoryStatusEx immediately before the ALLOCATE statement returns a value of available virtual memory of 2,118,221,824 bytes. ... So I'm getting an "insufficient virtual memory" failure when trying to allocate the array to a size which is 384.665 MB less than the amount of reported available virtual memory. ...
    (comp.lang.fortran)
  • Re: virtual memory leak? in asp.net app - OutOfMemory exception
    ... Doing so seems to allocate several hundred MBs of ... Loading the same XML stream again seems to re-use the allocated virtual ... Why is the app not releasing the virtual memory as it reaches is memory ...
    (microsoft.public.dotnet.framework.clr)