Re: memory not freed up?
cluenewbieblue@xxxxxxxxx wrote:
> Please point in right direction.
> I use the cvf compiler and notice after allocating and deallocating
> arrays (about 10-50MB per array) some memory is not actually available
> even though all arrays are deallocated.
What do you mean by "not actually available" ?
--
pa at panix dot com
.
Relevant Pages
- memory not freed up?
... I use the cvf compiler and notice after allocating and deallocating ... even though all arrays are deallocated. ... (comp.lang.fortran) - Re: Basic ASCII File Reading
... critical first step to almost anything like this - defining the problem. ... FJ appears to have guessed that the header is always exactly 7 lines. ... His involves allocating and deallocating, ... time consuming than resizing arrays. ... (comp.lang.fortran) - Re: ALLOCATABLE arrays
... > If try to create a very large array on the stack and you do not have enough ... > Allocating on the heap gives you access to a hell of a lot more memory (well ... Allocatable arrays are allocated on the heap. ... Automatic arrays are always allocated on the stack. ... (comp.lang.fortran) - Re: ALLOCATABLE arrays
... || If try to create a very large array on the stack and you do not have enough ... || Allocating on the heap gives you access to a hell of a lot more memory (well ... and "heap" (and there probably are/were some computers which don't/didn't ... | Automatic arrays are always allocated on the stack. ... (comp.lang.fortran) - Re: ordering integer array
... though it is a fair amount of work. ... the implementation of allocatable arrays is usually ... And the extra runtime work done by the application is going to be ... Allocating an array for the seed of a random number ... (comp.lang.fortran) |
|