File Handle leak? Was: Octave/Win32 new binary package (2.9.12)

[Benjamin Lindner]

> Hi,
> 
> A new binary package of Octave for Win32, based on 2.9.12 is available on
> http://www.dbateman.org/?page=octave&lang=EN. Up to now, it's more a
> release candidate than an official package. I'd like to find a few people
> willing to give it a try and report problems, such that it can maybe
> become
> more official after fixing (it's based on official releases of octave
> and octave-forge).
> Anyone interested? Thanks.
> 
> Michael.

I tested the binary on a w2ksp4 machine and found that somehow it seems to
leak file handles.
Using ProcessExplorer the handle count steadily increases during usage.

A simple command like 'upper("a");' entered at the prompt increases 
the file handle count by 2 for every command.
The command 'plot(1:10,1:10);' using the oplot-gl package increases 
handle count by 48 for every call.

However wrapping command in a loop does not increase for every call.
E.g. 'for n=1:1000, b=upper("a"); endfor;' increases handle count by 2 like a 
single call.

Also calling built-in functions like sin(), cos() don't increase handle count.

Looking at the open handles I can see multiple handles to one and the same 
script file (e.g. upper.m, or drawnow.m)
This looks like octave creating a handle when reading/parsing a  script file 
and not releasing it.
I have tested with all possible settings of ignore_function_time_stamp and the 
behaviour does not change.

Can anyone confirm this ?

benjamin

P.S:
starting octave --no-init-file lists 3 file handles to 
share\octave\packages\java-1.0.1\octave.jar
executing at the prompt 'upper("a");' lists 2 additional handles to 
share\octave\2.9.12\m\strings\upper.m
every additional 'upper("a");' adds 2 file handles to 
share\octave\2.9.12\m\strings\upper.m


-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail