| Re: Q: Efficient Memory handling and deallocation [message #4103] |
Thu, 04 May 1995 00:00 |
rutledge
Messages: 4
Registered: May 1995
|
Junior Member |
|
|
In article <3oaptn$oee@news.doit.wisc.edu>, Paul Probert <probert@uwmfe.neep.wisc.edu> writes:
> operating system's fault. But we figured out, as you did, that IDL
> doesn't deallocate the memory. One workaround is, at the beginning of
> your program, create and then immediately delete an array 2 or 3 times
> the size of your needs, and this will leave a hole big enough for many
> future reallocations.
Excuse my ignorance, and this is probably stating the obvious, but this
makes it appear that IDL keeps the heap memory allocated and cannot free
it up (until exiting). When I run my programs, that indeed seems to be the
case -- I can allocate my 200M worth of variables, deallocate them, and
IDL keeps the heap a monstrous size. This is silly (and wasteful of my
computer resources) as I don't use 200M for more than 5 sec, and there
are other applications on my computer which could use that.
Is there really no way to de-allocate the heaped IDL memory? I may
have to quit using it and go back to C and X, where I have some measure of
control.
Bob
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
