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

[Dan Sebald]

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

There is this bug report

https://bugreports.qt.io/browse/QTBUG-24795

that sounds like it might relate to the tryLock(3000) not waiting.

Version 4.8.6 of the code is here:

https://qt.gitorious.org/qt/qt/source/8ab1ad64620ff9d0453a326010d161ea68a63a2f:src/corelib/thread/qmutex_unix.cpp

If you have 64bit system (i.e., /usr/lib64), maybe this bug doesn't apply.  If
you are interested, you could try this patch 

https://savannah.gnu.org/bugs/download.php?file_id=33690

again but change

+  if (! _octave_qt_link->mutex.tryLock (3000))

to

+  if (! _octave_qt_link->mutex.tryLock (1500))

Maybe you will see a 1.5 second delay and proper exit behavior.

(If using just mutex.lock() works, we might go with that in any case and forgo
the timeout.)

    _______________________________________________________

Reply to this item at:

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

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