Bug #66579 Blank autosaved SQL files after crash
Submitted: 28 Aug 2012 15:08 Modified: 29 Oct 2012 0:50
Reporter: Timothy Liang Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.42 OS:Windows (Microsoft (build 8400), 64-bit)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[28 Aug 2012 15:08] Timothy Liang 
Description:
I had a BSOD while MySQL Workbench was open.  I restarted and opened Workbench.  It told me it detected unsaved changes.  When I opened the SQL editor, I found that eleven out of thirteen of the tabs were completely empty.

----- Developer Notes -----

MySQL Workbench CE for Windows version 5.2.42  revision 9752
Configuration Directory: C:\Users\Timothy\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft  (build 8400), 64-bit
CPU: 8x Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz, 8.0 GiB RAM
Current user language: English (United States)

How to repeat:
Open some new tabs, edit them, wait a few minutes, and then trigger a blue screen.
[28 Aug 2012 15:43] Timothy Liang 
I closed and reopened the SQL editor and now I have 18 tabs, with 14 of them empty.  I think this is because I discarded a few tabs before the crash.  Also, two of the non-empty tabs are duplicates of the other two.
[29 Sep 2012 0:50] MySQL Verification Team 
Please try version 5.2.44. Thanks.
[29 Oct 2012 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".