If this code hunk is reached because of the cleanup timeout, it is causing an abort and that may be what brings about the Windows message. I'm thinking now that was probably the wrong thing to do. Three interrupts might cause interpreter to exit. That may not make a difference, but maybe that will prevent some type of Windows or Linux dialog popup window.ģ) And the last one is to remove what may have been the source of problems in the Rarely will cleanup take five seconds, I'm hoping, so the last ditch terminate should be less likely now.Ģ) I changed the exit under the terminate condition from So I've attached an updated changeset that I think and hope is a solution that will do and not produce messages or corrupted settings files.ġ) I changed the final 2 second timeout for cleanup to 5 seconds. The ability to interrupt is close enough I suppose. The proper terminate/abort approach is discussed here:īut it would require a small change to the worker thread which I don't want to make for this solution nor ask any of the more maintainer oriented contributors to make. The Qt discussion lists mention how terminating can freeze up resource unexpected such as mutexes and so on. In any case, I think once we get to the point of terminating the interpreter (which is unadvised except for the last resort, what we are using it for) that all bets are off on how the program and system will work. I gather the message said something about improperly terminating unexpectedly. I really couldn't find much on how to suppress Windows from creating a message dialog.

What is gnu octave