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

[Dan Sebald]

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

Attached is another patch file, this time we'll use "lock" instead of
"tryLock".  "lock" returns a void because it blocks until it gets a lock,
i.e., completes the lock or never returns.

That lack of a 3 second wait is confounding.  tryLock(3000) is supposed to
wait three seconds before declaring a fail to lock.  Not fail immediately.

I'm guessing the original source of error here was a timing issue.  The fact
that _shutdown_confirm_result comes back from the signal emit unchanged
indicates the signal was, in fact, queued, not direct.  That agrees with the
thread affinity.  On the other hand, the printf() statements are somewhat out
of order from what they should appear if operating correctly.  It seems that
your system behaves slightly different than mine in the sense the threads
might be either operating on different CPUs or the CPU resource is shared
between threads in smaller time intervals.  In other words, the main_window
thread is getting ahead of the qt_link thread.  That's not a problem at all. 
If the attached patch works for you, we have a solution...

(file #33694)
    _______________________________________________________

Additional Item Attachment:

File name: use_lock-2015apr16.diff        Size:3 KB


    _______________________________________________________

Reply to this item at:

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

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