In my never-ending quest to demonstrate that I can make every possible mistake ...

Details for the issue

What did you do?

In the execute query window I generated a recursive select that failed to terminate.

What did you expect to see?

A "stop" button.

What did you see instead?

A busy-wait loop, spinning disk, unresponsive GUI.

The only thing I could do was take a screenshot of my SQL & kill the browser.

Two issues (and I think both constitute bugs)...

• There really needs to be a "STOP" button so that a query (or other operation) can be cancelled.
• The Execute SQL tabs should have a checkpointing facility (as editors and now webbrowsers do), so that when the browser, computer, or user crashes, work can be recovered.

Restarting the browser should offer to recover the session/execute SQL tabs.
(I had 8 open where I was trying to figure out how to make a tree-walking select work - the screenshot captured only one...)

I suppose that the browser could use a, er, database to journal user sessions with full roll-back and roll-forward ;-) But a simple text file (e.g. emacs session files) would do.

Useful extra information

The info below often helps, please fill it out if you're able to. :)

What operating system are you using?

• [x ] Windows: ( version: ___ )
• Linux: ( distro: ___ )
• Mac OS: ( version: ___ )
• Other: ___

What is your DB4S version?

• 3.10.1
• 3.10.0
• 3.9.1
• Other: ___

Did you also

• Try out the latest nightly version: https://github.com/sqlitebrowser/sqlitebrowser#nightly-builds
• Search for an existing similar issue: https://github.com/sqlitebrowser/sqlitebrowser/issues?utf8=%E2%9C%93&q=is%3Aissue%20