comp.lang.idl-pvwave archive: archive » IDL new graphics memory leak?

Home » Public Forums » archive » IDL new graphics memory leak?

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

Re: IDL new graphics memory leak? [message #93718 is a reply to message #93717]

Wed, 05 October 2016 06:51

Phillip Bitzer
Messages: 223
Registered: June 2006

Senior Member

> On 10/04/2016 02:39 PM, Helder wrote:
>> Did you try img.close instead of obj_destroy? Did this give the same result?
>> Also, if I do a lot of images, I would change the loop to something like this:
>>

This is exactly the problem. A MWE shows it explicitly:

help, /heap, /brief ;to start

img = IMAGE(/test)
img.close
help, /heap, /brief ;anything on the heap?

img = IMAGE(/test)
OBJ_DESTROY, img
help, /heap, /brief ;Oops!

Further, the setData method Helder suggested will be very handy as well!

Report message to a moderator

[Message index]

		IDL new graphics memory leak? By: belkaraza on Tue, 04 October 2016 04:56
		Re: IDL new graphics memory leak? By: Helder Marchetto on Tue, 04 October 2016 05:39
		Re: IDL new graphics memory leak? By: Markus Schmassmann on Tue, 04 October 2016 06:36
		Re: IDL new graphics memory leak? By: Phillip Bitzer on Wed, 05 October 2016 06:51

Previous Topic:	display GeoTIFF image automatically using cgGeoMap
Next Topic:	trying to convert map to graphic functions

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 17:51:27 PDT 2025

Total time taken to generate the page: 0.00221 seconds