Bug #84018 Autosave fails and generates error message
Submitted: 30 Nov 2016 15:09 Modified: 30 Dec 2016 17:41
Reporter: Brian Badge Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3.8 OS:Windows (Microsoft Windows 7 Enterprise Service Pack 1)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[30 Nov 2016 15:09] Brian Badge
Description:
Autosave constantly fails throwing an error message.
10:04:24 [ERR][ SqlEditorPanel]: Could not save snapshot of editor contents to C:\Users\RZN4X8\AppData\Roaming\MySQL\Workbench\sql_workspaces\Local_instance_MySQL57-1.autosave\{D3AF0184-13DC-4198-AAD1-7DC4420ADB19}.scratch: Failed to create file 'C:\Users\RZN4X8\AppData\Roaming\MySQL\Workbench\sql_workspaces\Local_instance_MySQL57-1.autosave\{D3AF0184-13DC-4198-AAD1-7DC4420ADB19}.scratch.5XZCRY': Permission denied
10:04:24 [ERR][      SqlEditor]: Could not auto-save editor PREDICTION*

How to repeat:
Edit SQL
[30 Nov 2016 17:41] MySQL Verification Team
: Permission denied?. Please check if your anti-virus application is blocking the save action. Thanks.
[1 Jan 2017 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[23 Feb 2018 2:20] John Hennessy
It happens constantly (Windows 10).  I suspect it is NOT anything to do with antivirus software because it still happens when I turn it off.  In my case, neither the individual files nor the directory is protected; in fact, I can  open an editor and change things right after Workbench grumbles.  The key, I believe, is the lock that Workbench puts on the directory (and removes when Workbench closes).  Since I can't delete the file while it's in use, I can't verify this (but I do ask "Why bother with the lock?  It's not like there's a lot of concurrent access going on."