[Octave-bug-tracker] [bug #44751] Failure to exit when running Octave in --no-gui mode

[Dan Sebald]

Follow-up Comment #22, bug #44751 (project octave):

[The "closenow = 40" is a mistake, I forgot a printf argument, but it doesn't
matter.]

That's odd.  The peculiar thing is that the confirm_shutdown_octave slot is
being called prior to the wait state on your system (or version of Qt).  In
other words, the "awake" is being done before the Octave core process goes to
"sleep".  That shouldn't happen across threads, as the 


  emit confirm_shutdown_signal ();


should be queued and not run.

I suppose there is a simple solution, which is to first put a bogus value into
what is to be returned and if after the emit is done the return value is no
longer bogus it means the slot was already run so no need to go into the wait
state.

But let me search around first as to why this signal hasn't been
queued--whether it has something to do with the construction of link and
main_window objects, or perhaps a change or optimization in the version of Qt
on openSUSE 13.2 and Debian wheezy.

I'll send a bug fix patch later this afternoon or evening.

    _______________________________________________________

Reply to this item at:

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

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