Stopping phix (bug?)
- Posted by irv Dec 22, 2020
- 2019 views
When I end a EuGTK program, the window(s) close and if I'm running from a terminal, the terminal prompt returns.
When I end a PhixGTK program in the same way, the window(s) remain on the screen - non-responsive - and you have to do a ctl-c on the terminal, which closes the non-responsive windows, and gets you back to a prompt.
Watching the process monitor, it shows p using 10.9 megs of memory and 320 megs of virtual memory.
Clicking on the window close button shows p still running, but memory and virtual memory are N/A. Only ctl-c on the term or killing p in the system monitor will destroy the window and return to the prompt.
Doing the same with Euphoria, Eu disappears from the process list as soon as you close the main GTK window.
Calling gtk_main_quit() before abort makes no difference.
This is especially a problem if you compile a program and run it by clicking on the file icon. There's no way to stop it, short of waiting for the "Non-responding" dialog and clicking on "force quit", which is after a long delay.
Why the difference between Eu and Phix?
