[SA 7.0.158 Pro] - Restore Tabs bug

[SA 7.0.158 Pro] - Restore Tabs bug

Whenever I start SQL Editor and try to restore tabs that have not associated with saved files, SQL Editor crashes. It works with saved files, however.

Could you please check SQL Assistant's log file in %APPDATA%\SQL Assistant\7.0\SqlAssist.log and if it writes any errors or exceptions to the log. If yes, please let us know what kind or errors/exceptions appear there.

That file was last modified yesterday. Besides, it's the log file for SQL Assistant. That works properly, it's SQL Editor that crashes. Where does it store its log?

	Quote:
	...it's SQL Editor that crashes. Where does it store its log?

I don't think there is a separate log. The exceptions should be handled by the same procedures.
I'm unable to reproduce this issue. Can you please check if it happens with specific scripts or with all scripts? also, does it depend on your database connection settings and auto-connect state?

Nothing relevant then in that file. I cleared the file completely yesterday, had a crash again today morning but the only entries in it were from yesterday evening.
It is triggered by any script that is in an unsaved tab. Right now I can only access a single MySQL server so I cannot test the other things you requested. Is there a way to reset that feature? Which folder(s)/file(s) do I delete/clear?

I believe you also work with SQL Server. Would it be possible to test it with a SQL Server connection?

I usually do but those servers are currently unreachable due to network outage and I don't have SQL Server installed on my machine. I might be able to try them tomorrow or next week.

I tried with MySQL connections and couldn't reproduce that issue. Would you mind attaching a screenshot of the Restore Tabs dialog. Maybe I can spot something on your screenshots different from mine.

If I can reproduce it, I can log an issue with how-to-reproduce steps, which would allow our development team to fix it quickly, otherwise it may take forever, until more info comes to light.

Here's a short video of what's happening here. I don''t think it has anything to do with connection type (MySQL or otherwise) because it crashes before trying to connect and those tabs having their contents saved in a file connect properly without crashing. I'm not sure whether is it relevant but I checked the name ~51EFAFD4.sql and ~5B7E298.sql and they didn't exist.

By the way, the crash that happened at the start of the video when I tried to close SQL Editor and chose not to save the file left no traces in the log file at %APPDATA%\SQL Assistant\7.0\SqlAssist.log.