octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Rik
Subject: [Octave-bug-tracker] [bug #44751] Failure to exit when running Octave in --no-gui mode
Date: Tue, 07 Apr 2015 19:10:16 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0

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

Sample code that repeatedly fails for me


./run-octave -f --no-gui
figure
drawnow XXXX
exit


The problem is outlined in bug #44759 for a special case of drawnow.  What is
happening is that the gh_manager is becoming locked, and due to an error or
other unusual code path, is not getting unlocked.  When Octave goes to exit it
checks with the octave_link to see whether there are windows outstanding and a
deadlock situation arises.

This isn't a problem for me if I use run-octave -f --no-gui-libs, implying
that the Qt libraries and octave_link need to be present.

While bug #44759 can easily be fixed.  It would probably be worth doing two
things.  First, providing a way for octave_link to recognize that exit was
called and override and locks in gh_manager.  Second, review the code which
locks and unlocks graphic figures to determine if there are other code paths
which can fail to unlock a figure after use.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]