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

[Dan Sebald]

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

Well, the Windows behavior certainly isn't acceptable.  After some digging, I
think I see why this is happening.  The QSettings is instantiated and deleted
by the worker thread.  Why that is, I don't know.  Doesn't seem very object
oriented to have something in another thread handling the settings for what is
in another thread.  I suppose the 1/2 second wait might not be long enough for
the worker to finish cleanup and the thread happens to be deleted right in the
middle of deleting that QSettings object.  (This can probably happen on Linux
too, it just might be Windows is a little slower cleaning up.)  I'll bring
this up on the discussion list.

The other issue is Windows displaying a message saying that Octave quit
unexpectedly.  (Another indication that the worker was in fact deleted rather
than finishing in the conventional way.)  It would be nice to figure out how
to prevent Windows from displaying such a message in that circumstance in the
cases where Octave is forcibly quit because it might be stuck.

    _______________________________________________________

Reply to this item at:

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

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