Sometimes, particularly on very long builds, pressing the "pause" button takes a long time to take effect. I click, the pause button becomes disabled, but the build keeps running for another 50 actions or more before finally pausing. Is this a known issue?
In particular, after the VS debugger issue I just mentioned (in General Issues), I clicked "No" then immediately "Pause" but it took a long time to actually pause.
There can be cases where having many actions running very quickly means the actions can get a little ahead of the IDE, so when you do something the IDE takes a couple of seconds to “catch up” with running actions. 50 actions sounds like a lot, though.
I’m currently looking at a build which is still running, hundreds if not thousands of actions after pressing the pause button. What’s especially odd is that there are many actions which pause for 3 seconds after running. If it was a synchronisation issue between the IDE and some other process, wouldn’t it “catch up” during these pauses?
It’s also odd that pressing the stop button (the blue square) stops it immediately. Why do they behave differently?
Actually it looks like the pause is the cause of the problem. Removing it made the problem go away. It was on a “run action list” action, if that helps.
Thanks for reporting this. I’m able to reproduce it in the current FB 5 build. It looks like sometimes the Pause button appears to be clicked, but the click doesn’t go through. The workaround is to click a couple of times, until it actually pauses. This only seems to be an issue when you’re running a lot of very fast actions with pauses after them.
The good news is that this is a bug in the underlying GUI architecture which appears to be fixed for the next major release. The bad news is we probably won’t be able to fix it before then.
Hmm, after I click the first time, the pause button becomes disabled, so I can’t click again. But not to worry, there are lots of workarounds, like using an external command to pause.