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

[Dan Sebald]

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

The performance test is interesting, i.e., the fact that Windows is so much
faster, but the two changesets affect code that is only exercised at exit.  I
can't imagine that is taking very much longer.  BTW, I sort of prefer the
performance test

start_time = cputime();
<process>
overall_time = cputime() - start_time()

The tic/toc are clock time and some aspects of Octave have a delay but really
aren't using CPU.

Well, back to the exit problems on Windows.  At first things looked good;
guess that's progress.  You'll have to characterize the behavior a little more
and maybe it will give some ideas.  Try some things like:

1) Correlate the zombie occurrence with the Windows popup message.  Are there
any times when there is a zombie and no message?  What is the Windows message
exactly?

2) See if there are any problems with a task that doesn't use so much memory. 
Try "pause(20)".  Maybe for the eigenvalues example the task of either
interrupting or exiting takes so long to clean up memory that the allotted two
second wait expires and the GUI kills the process and that is when a Windows
popup appears.  It could be that this cleanup takes a random amount of time,
sometimes finishing, sometimes not.

If the latter situation arises, we may need to figure out how to cleanly kill
a process in Windows.  Perhaps that isn't being done exactly right.

    _______________________________________________________

Reply to this item at:

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

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