comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Memory deallocate problem
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Memory deallocate problem [message #11522 is a reply to message #11298] Mon, 30 March 1998 00:00 Go to previous message
korpela is currently offline  korpela
Messages: 59
Registered: September 1993
Member
In article <351BDB75.7979@eosdis.atmos.uah.edu>,
Ying Jin <yjin@eosdis.atmos.uah.edu> wrote:
> Does anyone know the mechanism of memory deallocation of IDL ?
> My problem is :
> When I open several big arrays, I literally exhaust all the available
> memory, but I need more. And I don't care to deallocate the memory
> for the previous arrays.
> I have digged through the help and manual of the IDL version 4.0.3.
> It turns out that IDL seems to not want user to tackle the issue by
> themselves.

One possible solution is to use memory mapped files to create additional
virtual memory assuming you work under an OS that supports memory
mapped files. I wrote some code to solve a similar problem. A discussion
and the code is located at:

http://sag-www.ssl.berkeley.edu/~korpela/mmap/

There's also a discussion of memory deallocation in the IDL FAQ.

Eric

--
Eric Korpela | An object at rest can never be
korpela@ssl.berkeley.edu | stopped.
<a href="http://sag-www.ssl.berkeley.edu/~korpela">Click for home page.</a>
[Message index]
 
Read Message
Read Message
Previous Topic: bug in contour
Next Topic: POLY_FIT 5.0: inaccurate results. use 4.0 if possible.

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 04:30:56 PDT 2025

Total time taken to generate the page: 0.32020 seconds