Getting what looks like a repeat of an earlier problem. I step through a build, and it hits a step that triggers an error. In the current case, it can't write to a certain text file. But before that it was a different error and same result. FB then gets into a weird state where it's neither running nor stopped - the 'stop' button is the only available option. It also switches to the On Failure tab, but doesn't highlight a next step to run (there's only one step on that tab - exporting the log). When I press stop, it then freezes, becoming unresponsive.
I saw this before, and thought the problem was related to a corrupted log. But I've now renamed the log file, and the problem still occurs.
Steve