| Bug #74966 | tabs auto save | ||
|---|---|---|---|
| Submitted: | 21 Nov 2014 19:50 | Modified: | 13 May 2016 2:18 |
| Reporter: | maison sakamoto | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S2 (Serious) |
| Version: | 6.2.3,6.2.4 and 6.2.5 and 6.3.3.0 build 592 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
[21 Nov 2014 19:50]
maison sakamoto
[21 Nov 2014 19:51]
maison sakamoto
tab auto save
Attachment: workbench_tab_auto_save.png (image/png, text), 137.42 KiB.
[24 Nov 2014 7:14]
MySQL Verification Team
Thank you for the report. Did you upgrade from 6.1.x to 6.2.3? I haven't seen this issue with fresh installation of 6.2.3/6.2.4 and this issue is only reported post upgrade from 6.1.x to 6.2.x. Could you please provide below dir details from the problem instance? C:\Users\<User_Name>\AppData\Roaming\MySQL\Workbench\sql_workspaces>dir and then C:\Users\<User_Name>\AppData\Roaming\MySQL\Workbench\sql_workspaces\<workspace_name>>dir Please replace <User_Name> with actual username and <workspace_name> is the connection name. Thanks, Umesh
[24 Nov 2014 9:57]
maison sakamoto
O volume na unidade C nÆo tem nome.
O N£mero de S‚rie do Volume ‚ 7A66-3965
Pasta de C:\Users\maison\AppData\Roaming\MySQL\Workbench\sql_workspaces\Produ‡Æo_(_Windows_)-1.autosave
24/11/2014 07:51 <DIR> .
24/11/2014 07:51 <DIR> ..
24/11/2014 07:51 38 connection_id
24/11/2014 07:49 4 lock
24/11/2014 07:51 0 log.txt
24/11/2014 07:51 49 schema_tree
24/11/2014 07:51 0 {09E2404D-6A72-40AA-B3E2-20166733986E}.scratch
24/11/2014 07:51 0 {14C8AB5F-7328-4B35-A679-F0EA34FABCAD}.scratch
24/11/2014 07:51 0 {19397052-9157-4F16-A2E0-8BD46D322332}.scratch
24/11/2014 07:51 0 {22C15D29-25C8-4137-8541-BD52A5978524}.scratch
24/11/2014 07:51 6 {2D5A5698-2C58-48FF-8F60-B1915D0EBEAB}.scratch
24/11/2014 07:51 0 {4243A1E4-1CEA-483F-B1BD-64FBA11340DD}.scratch
24/11/2014 07:51 0 {5FE13710-9F34-423D-A807-6B00B1BF9F2E}.scratch
24/11/2014 07:51 220 {624CECAB-BF3B-4B72-8C66-6C5B6509D961}.scratch
24/11/2014 07:51 0 {7EE1B639-565E-4EE5-A8A5-B7F8F2DD5C57}.scratch
24/11/2014 07:51 0 {8D5885F6-8994-4B30-9099-45AC0E94605E}.scratch
24/11/2014 07:51 0 {A7EE6F4A-3DD6-446C-8679-C79CB5494982}.scratch
24/11/2014 07:51 5 {CC114B72-C1F5-4FEB-BFF0-5BA502292B6E}.scratch
24/11/2014 07:51 0 {CCDD3869-E05D-4457-A887-4D114876ED10}.scratch
24/11/2014 07:51 44 {DA6FAAB0-0EC5-45C0-ACBE-7AE01DF00B4E}.scratch
24/11/2014 07:51 0 {E5F7292B-9456-4297-A20D-FB09F7D4CBD8}.scratch
24/11/2014 07:51 0 {F1525712-BE40-4710-B81F-03FE35AC1163}.scratch
24/11/2014 07:51 0 {F4DB2EF8-AC87-46F6-95F7-A0A45FC516FA}.scratch
21 arquivo(s) 366 bytes
2 pasta(s) 149.707.640.832 bytes dispon¡veis
yes, I did upgrade 6.1.x to 6.2, gave me this error, as updated from 6.2.3 to 6.2.4 and continue with the same error.
[24 Nov 2014 10:15]
MySQL Verification Team
Thank you for the details. "Produ‡Æo_(_Windows_)-1.autosave" contains the autosave files scratches and so on the <workspace_name> is the connection name. Please backup this directory "Produ‡Æo_(_Windows_)-1.autosave" somewhere in safe location before doing any changes into that directory. Just for your info - .scratch contains editor contents, while .info contains the information about how it was stored what settings there were cursor pos etc, tab_order contains the order of the tabs in sql the editor tabs. Before 6.2.3 there was .autosave and .filename etc So, this is the place you can try to clean up. You'll need to remove the .autosave and and start over WB... Hope that this would resolve the issue.
[24 Nov 2014 10:23]
maison sakamoto
deleted the entire folder, deleted the instance too, but the error continues, the strange thing is that I have other instance and the other work, only this instance has problem.
[24 Nov 2014 10:32]
maison sakamoto
surprise, the instance name is the problem, was using standard characters utf8 if "Produção" char "ç" and "ã" generates this error, changed the name and the problem disappeared.
[24 Nov 2014 11:32]
MySQL Verification Team
Thank you for confirming... Closing the bug for now, please feel free to open if you hit this again. Thanks, Umesh
[24 Nov 2014 11:40]
maison sakamoto
Please Correct the bug to accept characters in utf8 format, or make a schedule to prevent accepted. So we avoid that other so-called like this to be opened again.
[24 Nov 2014 12:02]
MySQL Verification Team
Thank you for the feedback.
With the utf8 chars this is reproducible on WB 6.2.4
How to repeat:
1. Create new connection and save/name it as "Produção"
2. Connect to the instance using connection "Produção"
3. Open up few SQL/Query tabs, later on close all opened tabs before closing WB
3. Repeat step 2.. all zombie tabs reappear( in my local instance I see {1F96376F-7FCE-4296-B68F-C70537E52680}.scratch etc)
[19 Jan 2015 13:22]
MySQL Verification Team
Bug #75553 Marked as duplicate of this
[16 Mar 2015 5:47]
MySQL Verification Team
Bug #76326 marked as duplicate of this
[19 Mar 2015 11:54]
maison sakamoto
new version remains the same problem
[5 May 2015 13:53]
maison sakamoto
new version 6.3.3.0 build 592 yet
[8 Jul 2015 5:55]
MySQL Verification Team
Bug #77643 marked as duplicate of this
[4 Nov 2015 7:59]
MySQL Verification Team
Bug #79113 marked as duplicate of this
[19 Apr 2016 5:23]
MySQL Verification Team
Bug #81126 marked as duplicate of this
[13 May 2016 2:18]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Workbench 6.3.7 release, and here's the changelog entry: On Windows, after closing and reopening Workbench with several SQL Editor tabs open, the tabs names were hash values (instead of MySQL connection names) if the connection names contained non-standard text. Thank you for the bug report.
[27 Sep 2016 11:59]
MySQL Verification Team
Bug #83170 marked as duplicate of this
