On Mon, Nov 20, 2017 at 2:02 PM, John W. Eaton <address@hidden
<mailto:address@hidden>> wrote:
On 11/20/2017 02:41 PM, Daniel J Sebald wrote:
On 11/08/2017 01:17 PM, John W. Eaton wrote:
There have been about 70 changes made that address at least
50 bugs since 4.2.1, so it's probably time for a new release.
Are there any additional *critical* bugs that should be
fixed on stable before releasing 4.2.2?
I think this one is worth incorporating into 4.2.2 given that it
seems the solution is fairly straightforward to address a
segfault issue on MacOS:
bug #50025: Octave window freezes when I quit Octave GUI
https://savannah.gnu.org/bugs/?50025
<https://savannah.gnu.org/bugs/?50025>
Crashing even when exiting is kind of annoying as history might
not be saved and if run via a script octave returning an error
code could also cause issues.
The gist of it is that the GUI should wait for the worker
process to finish ending before moving on. I suspect on MacOS
there may be a problem of quitting the GUI when a thread is not
yet finished or is suspended. But there may be another means of
doing this rather than the technique in the submitted patch
(which itself is based on a Qt example). The signal could be
changed to have the blocking property. However, no one has
pursued that approach because few of us use MacOS regularly to test.
I remember reworking the way that the interpreter is started from
the GUI and the way things are cleaned up on exit. I did the work
on the default branch. Is this crash/hanging problem still present
on OS X with that branch?
I am not sure if this is the same problem or not, but 4.2.1 crashes on
Fedora 27 after exit (either gui or octave --no-gui; octave-cli is OK)
octave:1> quit
panic: Aborted -- stopping myself...
attempting to save variables to 'octave-workspace'...
panic: attempted clean up failed -- aborting...
Aborted (core dumped)
It did not in Fedora 26. perhaps it is related to Qt up date (it is
5.9.2 in FC27)