Re: Stopping phix
- Posted by irv Jan 02, 2021
- 1753 views
This works for interpreted code, but compiled still hangs.
Watching the System Monitor shows something interesting:
When you execute "test1" as a compiled program (either from a command line or by clicking on the compiled program icon), the System Monitor shows one instance of test1 running. Things work as they should.
When you click on a close button to shut down test1, a SECOND, "zombie" instance of test1 pops up on the sys monitor.
A fraction of a second after that, the first instance is also converted to a zombie. It's just like the TV show!
Then you get the "Not responding" window after a few seconds delay.
Another clue might be: when you run the program in the interpreter, from a terminal, you are returned to the terminal prompt after the program ends. e.g.
irv@irv-Mint19:/pgtk$
When you run a compiled version, you are not returned to the prompt until you do a "force quit" from the "Not responding" dialog.
