Comment 4 for bug 579332

I just managed to accidentally run into an infinite loop, the simulator was unusable then-this is really unfortunate, because it may even mean a loss of code, if you forgot to save your changes. Maybe there needs to be some small button or other UI item that allows the user to interrupt the simulator on demand?
Or at least a custom, configurable timeout interval-in milliseconds, so once the simulator spends more than this configurable amount of time running, the user could optionally stop it.

This works basically the same as in firefox, where a simple javascript may block the whole browser, after a certain amount of time firefox asks you if you want to keep running the code or cancel it.

This seems elegant enough for our situation, too. In particular because the user could easily customize this value on demand, so if a certain program does indeed take a couple of seconds (or longer) to fully complete, the user could configure a custom timeout value that is long enough.

Apart from that, separating the UI code from the simulator code would still be the right thing to do, in order to ensure that the UI remains responsive!