[Octave-bug-tracker] [bug #52024] Memory issue using File->Close from FLTK figure window

[Rik]

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

The issue is still not completely understood, but for a new FLTK figure the
function __add_default_menu__.m is called.  This creates the uimenu object for
the figure.  One of the menu entries is File->Close and the associated
callback is the pure piece of Octave code "close (gcf)".

The issue seems to be that FLTK detects the menu click, and then the uimenu
object attempts to run the callback code in an unwind/protect block.  The
callback code closes the figure which deletes the uimenu object.  When control
returns from the callback, the unwind protect block now has a non-existent
uimenu object.  That's all I can tell so far.  I don't have a good way of
solving this just yet.

    _______________________________________________________

Reply to this item at:

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

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