comp.lang.idl-pvwave archive: archive » Re: Graphics memory Allocation

Home » Public Forums » archive » Re: Graphics memory Allocation

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Graphics memory Allocation [message #32098]

Wed, 11 September 2002 06:35

David Fanning
Messages: 11724
Registered: August 2001

Senior Member

Andrew Fielding (a.fielding@icr.ac.uk) writes:

> After multiple runs of even very simple idl procedures that involve
> displaying images I eventually (usually around 10 runs) have to exit
> and restart IDL as the system is 'Unable to allocate memory'. I am
> running IDL 5.5 under win 95, which I know is not supported. Why does
> the memory not get 'flushed' at the end statement of a procedure? Any
> solutions would be gratefully received!

I'm not sure what "flushed" means in this context.
(I *have* heard the word "flushed" used in the Windows 95
context, but I don't think that is what you mean here.)

IDL does clean up memory at the end of each procedure.
Memory doesn't get returned to the operating system,
typically, but it does get reused internally. But, as
you well know, with an unsupported operating system,
all bets are off. :-)

Cheers,

David
--
David W. Fanning, Ph.D.
Fanning Software Consulting, Inc.
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155

Report message to a moderator

[Message index]

		Re: Graphics memory Allocation By: David Fanning on Wed, 11 September 2002 06:35
		Re: Graphics memory Allocation By: R.Bauer on Wed, 11 September 2002 06:23

Previous Topic:	Graphics memory Allocation
Next Topic:	Pointer Behavior Objects Vs Plain routines?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 00:38:27 PDT 2025

Total time taken to generate the page: 0.56281 seconds