[Top][All Lists]

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

Re: gnuplot bug in Windows release of Octave?

From: novakyu
Subject: Re: gnuplot bug in Windows release of Octave?
Date: Sun, 25 Nov 2007 17:52:24 -0800

On Nov 25, 2007 3:29 PM, Doug Stewart <address@hidden> wrote:
> novakyu wrote:
> > Hi,
> >
> > I'm using the Windows version of Octave from Sourceforge
> > (
> > with the binaries from, and although it works fine
> > most of the time, every once in a while, I get a strange error like
> > this:
> >
> > From what it looks like, this seems to happen when I plotted too many
> > times. In this particular run, I've issued the plot command maybe
> > somewhere between 300 to 400 times. For the moment, I can get around
> > the issue by making sure my functions return some save-able result
> > before it crashes (on ... what looks to me like a bug), but I would
> > very much like to know what could be causing the problem.
> >
> > Thanks,
> >
> > Andrzej
> >
> > P.S. I'm not sure if it matters, but I'm using Windows XP SP2 on a
> > Core 2 Duo with 1GB of RAM.
> >
> > P.S. Yes, plotting works fine for normal usage, and above directories
> > octave complains as not existing do exist.
> >
> I would watch the memory usage as you try and plot that many plots.
> Doug

'Sorry if I didn't make it clear---but it's 300 to 400 times plotting
on the same gnuplot window (over period of a couple hours; the
function I wrote is an interactive one), so the subsequent plot
commands should have cleared out the previous plots. If it is memory
issue, perhaps there is a memory leak (and a large one) either in
gnuplot or how gnuplot interacts with Windows version of Octave?

Tatsuro: As far as I can tell, this is not a problem with the path
name---after all, I was able to plot 300 to 400 times just fine before
the plot command failed (either gnuplot crashed ... or something else
happened that generated the error messages). If I have time later
today, I'll try to reproduce the behavior and if I can, file a proper
bug report.



reply via email to

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