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

Home » Public Forums » archive » Re: Memory allocation 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 allocation problem: [message #11009 is a reply to message #10991] Sun, 22 February 1998 00:00 Go to previous messageGo to previous message
Peter Mason is currently offline  Peter Mason
Messages: 145
Registered: June 1996
Senior Member
On Fri, 20 Feb 1998, I~nigo Garcia wrote:
> Well, I was afraid of something like this... I still find it a bug, whatever you
> say, they should find a way of freeing that memory !!! Can it be done with
> pointers ?? In a simple way, please, my brain is too small to fight with those
> beings.

Since version 5, IDL has been using a 3rd-party memory allocation library
called "SmartHeap". (At least, I know this is true for Win95 and suspect
it's true for other platforms.)
(Check out http://www.microquill.com/ for info on SmartHeap.)

SmartHeap functions differently on different platforms, especially with "large"
allocations (>64K). One would hope that a product like this would generally
be able to return large allocations to the operating system, but apparently
they haven't yet got this right for some operating systems.
Still, I'd say that RSI is on the right track using this stuff (mostly for
other reasons). If there was an easy-to-use solution to the memory-freeing
problem that some of IDL's platforms still exhibit, I'd expect it to be in
a product like this, sooner or later.

I don't think that there's a way around this right now.
I admit that I haven't tried to do this kind of thing, but from what I know,
if there was a solution (and it would be platform-specific) I think it would be
an ugly and very risky one involving C code and a sound knowledge of IDL
internals. Also, it would only address the variables you know about. IDL
goes through a lot of temporary variables, and it would still handle these its
own way.



Peter Mason
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Computing Speed
Next Topic: Re: PrintScreen

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

Current Time: Thu Oct 09 09:53:49 PDT 2025

Total time taken to generate the page: 0.80021 seconds