| Re: Scope_Varfetch "IDL workbench" train wreck [message #68677] |
Wed, 18 November 2009 18:55  |
wlandsman
Messages: 743
Registered: June 2000
|
Senior Member |
|
|
On Nov 18, 3:07 pm, Heinz Stege <public.215....@arcor.de> wrote:
> Seems to be a bug in the IDL 7.1 workbench. The workbench craches
> with a lot of java errors in { x86 Win32 Windows Microsoft Windows
> 7.1.1 Aug 19 2009 32 64}.
>
A little bird told me that ITTVIS had discovered this bug about 3
weeks ago, and already has made the fix, which will be included in the
next IDL patch release. --Wayne
|
|
|
|
|
|
| Re: Scope_Varfetch "IDL workbench" train wreck [message #68689 is a reply to message #68688] |
Wed, 18 November 2009 11:36  |
penteado
Messages: 866
Registered: February 2018
|
Senior Member
Administrator |
|
|
On Nov 18, 4:19 pm, wlandsman <wlands...@gmail.com> wrote:
> I recently received a note from a user saying that my procedure
> readcol.pro
> (http://idlastro.gsfc.nasa.gov/ftp/pro/misc/readcol.pro) - one of
> many such procedures to read an ASCII file into IDL variables -- was
> taking ~100 times longer to run from the IDL workbench than from the
> IDL command prompt. I of course replied that this was complete
> nonsense, and that the interface used to call the procedure shouldn't
> affect its speed.
>
> Of course, when I tested this, a run that took under 1 second from the
> command prompt completely hung my Mac (x86_64 darwin unix Mac OS X
> 7.1 Apr 21 2009 64 64) when run from the Workbench. My Linux box
> was not quite as bad but also eventually hung with messages such as
>
> java.lang.OutOFMemoryError: unable to create new native thread
> java.lang.ArrayIndexOutOfBoundsException: 2601
>
> The culprit apparently is my use of SCOPE_VARFETCH. readcol.pro
> calls SCOPE_VARFETCH thousands of time for a large file, since it
> writes data directly into the output variables, and uses a
> SCOPE_VARFETCH call for each item written.
>
> Below is a little test program to be called with
> IDL> test, x1,x2,x3,x4,x5,x6,x7,x8,x9
>
> I find it runs instantly from the IDL command line but takes very long
> or hangs the IDL workbench. --Wayne
>
> pro test,a,b,c,d,e,f,g,h,j
>
> vv = ['a','b','c','d','e','f','g','h','j']
> for k=0,8 do begin ;Create output variables
> res = execute(vv[k] + '=fltarr(5000)' )
> endfor
> for jj=0,4999 do for k=0,8 do (scope_varfetch(vv[k],Level=0))[jj]=
> float(jj)
> return
> end
Very odd. It ran in the Workbench in about the same time, but after it
is done, a lot of error messages get written to the terminal from
which I called the Workbench, and after a few seconds, the Workbench
dies with the same kind of error messages. This is with IDL 7.1 on
Fedora 11 64 bit.
I tried turning off some visualizations (I though that Debug and
Variables might be doing something to keep track of the call stack and
local scope variables, and the problem might be there), but saw no
change. I would write to ITTVIS, since this is definitely a bug.
|
|
|
|
|
|
| Re: Scope_Varfetch "IDL workbench" train wreck [message #68693 is a reply to message #68691] |
Wed, 18 November 2009 11:01 |
Foldy Lajos
Messages: 268
Registered: October 2001
|
Senior Member |
|
|
On Wed, 18 Nov 2009, wlandsman wrote:
> Of course, when I tested this, a run that took under 1 second from the
> command prompt completely hung my Mac (x86_64 darwin unix Mac OS X
> 7.1 Apr 21 2009 64 64) when run from the Workbench. My Linux box
> was not quite as bad but also eventually hung with messages such as
>
> java.lang.OutOFMemoryError: unable to create new native thread
> java.lang.ArrayIndexOutOfBoundsException: 2601
>
> The culprit apparently is my use of SCOPE_VARFETCH. readcol.pro
> calls SCOPE_VARFETCH thousands of time for a large file, since it
> writes data directly into the output variables, and uses a
> SCOPE_VARFETCH call for each item written.
>
>
> Below is a little test program to be called with
> IDL> test, x1,x2,x3,x4,x5,x6,x7,x8,x9
>
> I find it runs instantly from the IDL command line but takes very long
> or hangs the IDL workbench. --Wayne
>
>
> pro test,a,b,c,d,e,f,g,h,j
>
> vv = ['a','b','c','d','e','f','g','h','j']
> for k=0,8 do begin ;Create output variables
> res = execute(vv[k] + '=fltarr(5000)' )
> endfor
> for jj=0,4999 do for k=0,8 do (scope_varfetch(vv[k],Level=0))[jj]=float(jj)
> return
> end
There is no time difference between the CLI and GUI runs in IDL 7.0 on 64
bit linux. (It's a fresh openSUSE 11.2 machine with the OpenJDK 1.6 java
environment.)
Temporary buffers will solve your problem:
pro test,a,b,c,d,e,f,g,h,j
vv = ['a','b','c','d','e','f','g','h','j']
ptmp=ptrarr(9)
for k=0,8 do begin ;Create output variables
ptmp[k] = ptr_new(fltarr(5000))
endfor
for jj=0l,4999 do for k=0,8 do (*(ptmp[k]))[jj]=float(jj)
for k=0,8 do begin
(scope_varfetch(vv[k],Level=0))=temporary(*(ptmp[k]))
endfor
ptr_free, ptmp
return
end
(Even the EXECUTEs have vanished :-)
regards,
lajos
|
|
|
|
| Re: Scope_Varfetch "IDL workbench" train wreck [message #68694 is a reply to message #68693] |
Wed, 18 November 2009 10:52 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
wlandsman writes:
> Below is a little test program to be called with
> IDL> test, x1,x2,x3,x4,x5,x6,x7,x8,x9
>
> I find it runs instantly from the IDL command line but takes very long
> or hangs the IDL workbench. --Wayne
Yikes! It broke my Windows machine running IDL 7.1 from
the Workbench. JAVA out of memory error.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: Scope_Varfetch "IDL workbench" train wreck [message #68853 is a reply to message #68677] |
Mon, 23 November 2009 08:56 |
bokubo
Messages: 38
Registered: July 2006
|
Member |
|
|
On Nov 18, 7:55 pm, wlandsman <wlands...@gmail.com> wrote:
> On Nov 18, 3:07 pm, Heinz Stege <public.215....@arcor.de> wrote:> Seems to be a bug in the IDL 7.1 workbench. The workbench craches
>> with a lot of java errors in { x86 Win32 Windows Microsoft Windows
>> 7.1.1 Aug 19 2009 32 64}.
>
> A little bird told me that ITTVIS had discovered this bug about 3
> weeks ago, and already has made the fix, which will be included in the
> next IDL patch release. --Wayne
The fix is CR56369 and it is now available in the IDL 7.1.2 patch
release. Please note, you will need to contact ITT VIS Technical
Support (TechSupport@ittvis.com) for the link to download this patch.
Be sure to mention your OS platform and architecture (32 or 64 bit).
Other than this CR, this patch releas fixes an issue with extended
ascii characters.
Bill Okubo, IDL Product Manager
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
