octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #34631] MinGW - fubarred Octave 3.4.+ after many plots
Date: Mon, 31 Oct 2011 06:01:15 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 Iceweasel/6.0.2

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

I don't see problems with either of your examples on my Debian system, but
opening plot windows when using gnuplot does require a separate gnuplot
process and a separate pipe for communication, so those may be counting
against some process limits you have.

Also, when using fltk, opening 400 plot windows on my system caused Octave to
use around 2GB of memory, so maybe that is causing trouble for you as well.

If the problems are only related to your system running out of resources, then
I'm not sure that is a bug in Octave.

With OpenGL graphics, I don't see a problem with adding many text objects to a
plot (I tried 10,000 and it worked OK on my system, though it took nearly 10
minutes and caused Octave's virtual process size to grow to around 7GB). 
However, I don't expect that to work very well at all with gnuplot.  Graphics
with gnuplot is probably never going to be very efficient, so I would not
worry too much about that and instead focus on improving the implementation of
graphics with OpenGL.

Even with OpenGL, the resource use might be too high.  Maybe we could improve
that.

So the first thing to do here is determine whether this is an actual bug in
Octave or just a problem with resources that happens to have worse
consequences on Windows systems.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]