Somehow corrupted Workset

[S. Studeny]

Hi Marco,

recently on 16.0.4.2161 I have experienced with corrupted workset. Windows were restarted automatically due to night self-update and next morning I started PLSQL developer with error about It can't read some file (I forgot to do screenshot) and half of windows opened in workset were missing content (are empty).
I'm right, that previous content of workset windows are lost now after being opened with error and left empty, since there is autosave active?

Best Regards,
Stanislav

 

[Marco Kalter]

If PL/SQL Developer is unable to finish the workset save operation during a Windows shutdown, the previous version of the workset contents should have been preserved. If there are now empty windows then this would be a bug.

Can you start the Windows Explorer and go to %APPDATA%\PLSQL Developer 16\Worksets (e.g. C:\Users\\AppData\Roaming\PLSQL Developer 16\Worksets)? Can you check if there is a directory with the name .tmp? This directory might hold a previous version of your workset contents.

 

[S. Studeny]

Hi Marco,

no, there are no .tmp files left. Today, I lost half of another Workset, but not during windows restart. I closed (on multiple PL/SQL Developers simultaneously running) all Worksets with Close button. Then restarted PC and opened again. Half of windows in workset said "Error reading file" and windows were empty. I saw only half of files in AppData/Roaming/../Worksets/Worksetname .... (and no .tmp files at all). After clicking on empty windows, desktop.0XX files has been created with zero size on FS, oops. See screenshot.

Best Regards,
Stanislav