[Octave-bug-tracker] [bug #44485] GUI: File | Exit from main menu doesn't work when Octave is busy

[Dan Sebald]

Follow-up Comment #19, bug #44485 (project octave):

When disappeared without a trace, was that when there were no modified files
in the editor?

Also, is it possible that the backtrace appeared in the GUI terminal window
which disappeared so quickly it's barely noticeable?  When the GUI is
launched, at first the OS terminal window receives the standard-error output,
but then the GUI takes hold of that.  On shutdown, the GUI gives the stderr
output back to the terminal window.  There could be a race condition between
that output redirection and the Octave core worker processes aborting.  In one
case the GUI might close before worker process displays a message, in another
case after.

I think we should get a consensus on the expected behavior.  I'm alright with
a backtrace output.  The shutdown is forced, after all, and the force
operation is achieving what is wanted.  I'm a little reluctant to design it to
issue an interrupt and then attempt exit again after the interrupt, because if
the problem with the core isn't solved with an interrupt (i.e., it is truly
stuck, as opposed to merely busy), then that strategy becomes and indefinite
loop.

    _______________________________________________________

Reply to this item at:

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

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