comp.lang.idl-pvwave archive: archive » freeing memory in programs

Home » Public Forums » archive » freeing memory in programs

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

Re: Freeing memory [message #7028 is a reply to message #3933]

Thu, 12 September 1996 00:00

rigby
Messages: 16
Registered: September 1995

Junior Member

In article 31DF@irc.chmcc.org, Phil Williams <williams@irc.chmcc.org> () writes:
>
> I have a function that reads data and does some base processing. As the
> procedure is running I monitor my system memory using SGI's sysmon.
> After the function is complete I use some % of memory.
>
> IDL> help,/mem
> heap memory in use: 13710221, calls to MALLOC: 25781, FREE: 25676
>
> I then save all the data to a file and quit idl.
>
> I then start idl and restore the data and compile the function and there
> is less memory used.
>
> IDL> help,/mem
> heap memory in use: 13709644, calls to MALLOC: 119, FREE: 14
>
> My question is why?

I don't know if it explains your observations, but the IDL command
history buffer uses up heap memory. Notice what "help,/mem" returns
as the history list gets longer.

---
--
Wayne Rigby
GE Corporate Research and Development
rigby@crd.ge.com

Report message to a moderator

[Message index]

		freeing memory in programs By: pjclinch on Thu, 23 March 1995 07:03
		Re: Freeing memory By: Christian Soeller on Fri, 13 September 1996 00:00
		Re: Freeing memory By: rigby on Thu, 12 September 1996 00:00

Previous Topic:	Slide_Image (widget_draw) Scollbar-Position ?
Next Topic:	labview news group

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Nov 29 00:35:19 PST 2025

Total time taken to generate the page: 0.71675 seconds