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

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

[Octave-bug-tracker] [bug #45366] Two objects not cleaning dynamically a


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #45366] Two objects not cleaning dynamically allocated widgets leading to crash at exit
Date: Wed, 10 Aug 2016 05:03:18 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0

Follow-up Comment #12, bug #45366 (project octave):

The patch that was applied was merely to fix seg faults sometimes appearing at
exit because some GUI objects were left active and without a parent.

You may be thinking of the patch here:

https://savannah.gnu.org/bugs/?func=detailitem&item_id=44485

the intention of which was to allow the GUI to exit even though the core is
active or stuck.  I felt like I came close to solving that one, but at some
point it started to feel too convoluted so I cried uncle, I guess.

The strategy I think is the right one.  If the user selects "exit" and the
core is busy or stuck the GUI does not get an acknowledgement so sits silent. 
So what I had done was start a Qt timer at the time of exit and if after half
a second or so with no acknowledgement the timer expires and causes a dialog
box to appear asking if exit should be forced.  (We don't want to toss
someone's possibly long-running job just because they accidentally select
close of the GUI window or type cntrl-Q when trying to close some other
application's window.)  But that's not all of it.  Say the dialog box is
displayed and THEN the acknowledgement comes.  Well, then we have to force
that dialog closed even though the user hasn't selected anything so that the
GUI can continue on and exit.  Oh, and the other thing is that one has to
create some variable to block MULTIPLE exits with cntrl-Q or whatnot so that
the dialog box doesn't appear more than once.

It just felt like it was getting to be too complex such that there might be a
better way.  I could get active on that

https://savannah.gnu.org/bugs/?func=detailitem&item_id=44485

patch again if something is needed for the next release.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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