[Top][All Lists]

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

[Octave-bug-tracker] [bug #55908] Closing plots much slower in Octave 5.

From: Rik
Subject: [Octave-bug-tracker] [bug #55908] Closing plots much slower in Octave 5.1.0
Date: Mon, 18 Mar 2019 00:32:36 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

Follow-up Comment #10, bug #55908 (project octave):

This is very strange.  I changed the BIST test in gcbo to

%! h = gcbo ();
%! if (! isempty (h))
%!   keyboard;
%! endif
%! assert (isempty (gcbo));

and then ran 'make check'.  It does stop at the keyboard statement and I can
check the handle which is valid, according to ishghandle().  The "type" of the
handle is "line", but  if I look at the properties I see it contains one
called "basevalue".  This is not a property that a default line object has.  A
stem, bar, or area graph might have a basevalue property which may mean it is
left over from one of those BIST tests.

If I check the root object, I see that the "callbackobject" property does
contain this handle.  However, gcbf returns [] so there is no active figure. 
I wonder if something is going wrong with deleting/closing figures and the
root object is not being updated properly.

If I follow the hierarchy up.  The parent of the "line" object is an axes
object which is valid.  The parent of the axes object is the figure object 1. 
And the figure is not valid, so how the axes exists is unknown.


Reply to this item at:


  Message sent via Savannah

reply via email to

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