[Octave-bug-tracker] [bug #44485] GUI: File | Exit from main menu doesn't work when Octave is busy

[Philip Nienhuis]

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

I wouldn't mind the performance differences between Windows and Linux that
much. Rik and I did some tests a while back and arrived at the same results.
But then I hadn't thought of equally optimimized libraries - on Linux Octave
uses the distro libs, on Windows Octave uses (I suppose) highly optimized
cross-built libs and OpenBlas. When I have some time I'll make an mxe native
build on Linux to be able to compare a bit better.

On topic:
I hadn't thought of clean-up time,good suggestion! Indeed, before all 4 cores
are invoked after submitting the eig() command it takes a few seconds and
assigning all that RAM also takes time.

OK new tests:
=============

1th run:
--------
pause (20)
File | Exit, Force Exit:  clean shutdown, no zombie process, but qt-settings
got fubarred completely.

2nd run:
--------
<changed some screen layout from the restored qt-settings backup>
pause (20)
Ends cleanly. Following octave-gui.exe in Task Manager I see that after
disappearing from screen, the process hangs around 1 second or so (cleaning
up?)

3rd run:
--------
pause (30)
<qt-settings in 2nd run hasn't been changed => clean exit apparently doesn't
touch qt-settings>
Didn't end cleanly: got Windows pop-up

4th run:
--------
<qt-settings still hadn't been touched in run 3, it seems>
Ended clean

5th run:
--------
no clean end

:
etc

I also tried again with [V, D] = eigs (rand (1e4)); - ended cleanly.

Conclusions:
============
- About half of the tries (in the 10 attempts reported here) end in what
Windows thinks is a crash, the other half exits cleanly

- I see no difference between eigs(1e4) and pause (20)

- qt-settings is only rarely affected. Until now, with the previous report
included + many many forced exits with the previous patches, I've only hit a
fubarred qt-settings twice (and there's bug #45459 that perhaps is related)

- In Task Manager I always see a process "FMAPP.exe" [*] appear for 4-5
seconds whe the Forced Exit popup window appears. It is related to my Lenovo
laptop's audio system, so that triggered me to wonder if it pops up in the
course of ending Octave's audio system? and is Octave's audio system shut down
gracefully?

- This time I didn't note zombie octave-gui.exe processes but I did find a
zombie process "conhost.exe" - it must have been started through Octave
(conhost.exe is a component of the Windows process that runs the terminal)

What I could do is put the binary installer in my dropbox that other Windows
users can try it out as well. My dropbox upload is very slow however (usually
takes overnight). Anyway would this help?


    _______________________________________________________

Reply to this item at:

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

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