comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
Home » Public Forums » archive » Re: Asynchronous IDL_IDLBridge causing memory leak
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: Asynchronous IDL_IDLBridge causing memory leak [message #72310] Tue, 31 August 2010 08:31 Go to previous message
Seth Johnson is currently offline  Seth Johnson
Messages: 4
Registered: August 2010
Junior Member
On Aug 30, 10:02 am, Seth Johnson <seth.spjoh...@gmail.com> wrote:
> On Aug 30, 8:35 am, Bennett <juggernau...@gmail.com> wrote:
>
>
>
>> On Aug 27, 2:39 pm, Seth Johnson <seth.spjoh...@gmail.com> wrote:
>
>>> Sorry, I realized there was a mistake in the second example, it should
>>> be:
>
>>> oBridge=OBJARR(5)
>>> FOR chain=0,4 DO BEGIN oBridge[chain]=Obj_New('IDL_IDLBridge')
>
>>> FOR i=0,999 DO BEGIN
>>>    FOR chain=0,4 do BEGIN
>>>       a=bindgen(1E4,1E3)
>>>       oBridge[chain]->SetVar,'a',a
>>>       oBridge[chain]->Execute,'a=a+a',/NOWAIT
>>>    ENDFOR
>
>>>    FOR chain=0,4 DO WHILE oBridge[chain]->Status() NE 0 DO wait,0.0001
>>> ENDFOR
>>> OBJ_DESTROY,oBridge
>
>>> I do not destroy the objects until the very end as there are
>>> parameters and routines that need to be loaded into each IDL_IDLBridge
>>> for various computations in addition to parameters that change with
>>> every iteration.  Destroying and recreating would be a rather large
>>> boon to processing time while the initial problem caused by
>>> asynchronous operation still remains.
>
>> I've noticed that leak in 6.3 but not in 7.0+.  Which version are you
>> running?
>
> Strange, I have tested this on IDL versions 7.0 and 7.1, both of which
> produce the leak.  Could the cause perhaps lie in the setup or one of
> the required packages?  I have noticed while testing on different
> machines that 7.0 and 7.1 use different versions of the shared library
> libstdc++.so.

It is not the most elegant of solutions, but I have found a temporary
work around for the memory leak. Rather than calling the asynchronous
processes from the main routine, I create a single child process that
then creates its own children and performs the asynchronous calls
similar to:

oBridge=Obj_New('IDL_IDLBridge')
oBridge->SetVar,'a',a
oBridge->Execute,"oBridge=Obj_New('IDL_IDLBridge')"
oBridge->Execute,"oBridge->SetVar,'a',a"
FOR i=0,999 DO BEGIN
tmp=memory()
oBridge->Execute,"oBridge->Execute,'a=a+a',/NOWAIT"
print,memory(/high)
WHILE oBridge->GetVar('oBridge->Status()') NE 0 DO wait,0.0001
ENDFOR

The child process (and its children) do not appear to leak memory as
the parent call does. I find it rather peculiar that this method
works, even after loading the IDL startup file into the child
processes.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Is it possible to generate an error when it is tried to multiply matrix with different dimensions?
Next Topic: Re: Speeding up data crunching using IDL_IDLBridge with asychronous execution

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

Current Time: Wed Oct 08 15:36:54 PDT 2025

Total time taken to generate the page: 0.00401 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.7.
Copyright ©2001-2013 FUDforum Bulletin Board Software