[Octave-bug-tracker] [bug #49515] Octave aborts on exit under some conditions with --eval CODE

[Dan Sebald]

Follow-up Comment #9, bug #49515 (project octave):

The idea with the sleep is a sort of handshaking with the GUI.  I'm fairly
certain other problems were run into, at the time, if the core just shut down
the GUI.  There might be open files, for example, or something else that
created timing issues.  So, I know that the sleep was put in so that the GUI
did its thing and then awoke the core process when it was done with all its
cleanup.

That is probably where the comment "assume it doesn't take a day" comes from,
i.e., it shouldn't take a day for the GUI user to answer the question "Save
this file".

Anyway, it sounds like there might be more than one thread waking up the core
thread.  That of course doesn't work in this scenario.  It would need to be
something more sophisticated like:

Confirm Shutdown Python Thread
Sleep until Python thread awakes core
Confirm Shutdown GUI Thread
Sleep until GUI thread awakes core

Or have some flags so that the core keeps going into a sleep state and upon
waking checks that all flags have been set, otherwise go back to sleep.


    _______________________________________________________

Reply to this item at:

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

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