[Octave-bug-tracker] [bug #34631] MinGW - fubarred Octave 3.4.+ after many plots

[Philip Nienhuis]

Follow-up Comment #1, bug #34631 (project octave):

Inspired by Nitzan's findings I could simplify the test case.

Running:


max_figs = 200;
for ii=1:max_figs; figure; plot (1:10); title (sprintf ("Plot %d", ii)); sleep
(0.1); endfor; pause; close all;


with either graphics_toolkit one can easily spot at which plot no. Octave gets
mixed up.
Changing the max_figs value to a value less than that number, Octave's
internal state seems to get reset.

E.g., on my machine (WinXP SP3, Core Duo 2.5 Ghz, 2 GB RAM), with gnuplot,
Octave gets mixed up while processing plot 84.
Setting value of max_figs to 82 will allow this loop to be run over and over;
so apparently the potentially offending internal state gets reset by a "close
all".

With fltk / OpenGL, Octave hangs after the 39th plot. 
Hitting <Return> makes Octave disappear (it crashes hard).
By experimenting it turned out that (at least in my case) a value of 19 for
max_figs is the max to safely return out of the loop.

So the behavior for gnuplot and fltk is different. I wouldn't know if these
are separate bugs.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?34631>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/