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

Home » Public Forums » archive » obj_destroy on IDL_IDLBridge hangs sometimes
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: obj_destroy on IDL_IDLBridge hangs sometimes [message #72241 is a reply to message #72073] Fri, 20 August 2010 06:20 Go to previous message
d.rowenhorst@gmail.co is currently offline  d.rowenhorst@gmail.co
Messages: 10
Registered: August 2008
Junior Member
On Aug 12, 4:43 pm, Alfred de Wijn <agdew...@gmail.com> wrote:
> Hi,
>
> I've been playing around with IDL_IDLBridge objects lately.
> Everything seems to be working fine until I try to destroy the
> bridges.  Here's some code that demonstrates the problem:
>
> ncpus = 4 ; or any other number you like
> bridges = objarr(ncpus)
> for i=0,999 do begin
>   print, 'building bridges...'
>   for cpu=0,ncpus-1 do bridges[cpu] = obj_new('IDL_IDLBridge')
>   print, 'burning bridges...'
>   for cpu=0,ncpus-1 do obj_destroy, bridges[cpu]
>   print, 'loop '+string(i)+' done'
> endfor
> end
>
> On my Linux systems (both 32 and 64-bit), this will eventually hang
> while calling obj_destroy.  It appears that loop number 27 is
> typically the one where things go wrong, but I've seen it fail earlier
> too.  When ncpus is larger, e.g., 16, failure is pretty much
> guaranteed in the first loop.  Does anyone know what's going on?  Is
> this a known issue?
>
> I'm not particularly familiar with IDL object internals, so it's
> likely I'm doing something stupid.  Any help appreciated.
>
> Thanks,
> Alfred

I can't help, but will verify that I am having the same issue on Mac
10.6.4.
[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: Re: Negative indexing and the WHERE function in IDL 8.0
Next Topic: WRITE_FITS error

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

Current Time: Fri Oct 10 08:58:20 PDT 2025

Total time taken to generate the page: 1.11929 seconds