Game does not exit when in loop.

[pixelfck]

When the game is in a loop, and I exit it with ALT+F4, the game seems to close but it is still active and needs to be killed in the task manager.

The easiest option to reproduce this is to build an endless loop and exit the game. I was however able to reproduce it with non-endless (but long running) loops as well, so I guess this may be the case for every loop.

I've had this happen with (for ...), (loop ...), (enum ...) and (enumwhile ...).

~Pixelfck

[Aury]

Does it spin up one cpu core to full? That might be related to what I was experiencing (But in my case it was simply opening & closing it often enough to catch it in a loop..)

[george moromisato]

When the game is in a loop, and I exit it with ALT+F4, the game seems to close but it is still active and needs to be killed in the task manager.

The easiest option to reproduce this is to build an endless loop and exit the game. I was however able to reproduce it with non-endless (but long running) loops as well, so I guess this may be the case for every loop.

I've had this happen with (for ...), (loop ...), (enum ...) and (enumwhile ...).

~Pixelfck

Definitely a bug, but unfortunately not easy to fix. If the main thread is caught in a loop, then it can't get any window manager events. There are several solutions to this, but none are easy. The biggest problem is that there are dozens of places where the execution engine is called from (both in the main thread and in background threads). I would have to change all of those places.

[pixelfck]

I don't think it is a high priority bug, unless it is related to the one Wolfy experienced. On my system, my single core is not used in full by the Transcendence process, but since I'm on a netbook with only one core, it may be different from a normal multicore machine.