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 + MSVC - fubarred Octave 3.4.+ a


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #34631] MinGW + MSVC - fubarred Octave 3.4.+ after many plots
Date: Thu, 22 Aug 2013 19:38:15 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6

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

Interestingly, or intruigingly, with a 3.7.6+ MingW build cross-compiled (MXE)
yesterday (hg 17304:4c7ee36f591d) this bug doesn't occur. Neither with
octave-cli nor with the GUI version.

According to Windows Task manager (WinXP SP3 here) the GUI version starts with
around 526 handles, which varies by only a few extra while producing the 34
plots in my example script.
The CLI version starts with 202 handles which slowly climbs to 221.

I doubt if (for this very build) the file handles do matter much - closing all
34 plots just makes one handle close (in Task manager) (both CLI and GUI
version).

*BUT....*
A previous 3.7.5 MXE build (cross-compiled 3 days ago) made with the very same
MXE environment (on my Linux box) starts with 201 handles, each plot (w 3
subplots) adds varying amounts of handles (8 - 30) until problems start with
730 handles.

IMO this is definitely a font (overflow) issue - after the 22th plot figure
there's no more text added to the plots, and then the number of handles
doesn't increase anymore.

Moving the mouse cursor over a plot provokes a lot of the following pair of
error messages scrolling over the screen:

:
warning: ft_manager: unable to load font:
C:/WINDOWS/fonts/LinLibertine_R_G.ttf
warning: ft_render: unable to load appropriate font
:


Puzzling...





    _______________________________________________________

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]