MySQL Bugs: #75015: cannot save files; MySQL Workbench crashes; auto-save ok

Bug #75015	cannot save files; MySQL Workbench crashes; auto-save ok
Submitted:	26 Nov 2014 21:43	Modified:	23 Dec 2015 13:02
Reporter:	Ania Mitros	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	6.2.4	OS:	Windows (Windows 7 Enterprise, Service Pack 1, 64 bit)
Assigned to:		CPU Architecture:	Any

Description:
To install I downloaded and ran mysql-workbench-community-6.2.4-winx64.msi on my Windows 7 Enterprise 64-bit laptop (17" hp ZBook). MySQL Workbench opens, connects to a database server, and returns queries. However, when I attempt to save the query results to a file or attempt to save the query scripts, the moment I click on the floppy disk icon MySQL Workbench crashes. When I reopen MySQL Workbench, the scripts are there so apparently were successfully auto-saved. I uninstalled and reinstalled and had the same problem. I just installed the prerequisite Microsoft .NET Framework 4 Client and Visual C++ Redistributable for Visual Studio 2013 a couple days ago (11/24/2014, probably) so have fairly recent versions of those. I will try to install the 32 bit version and, if that fails, then try older versions in hopes that one of them works, suspecting some incompatibility between my brand new client and some older server.

How to repeat:
Install  mysql-workbench-community-6.2.4-winx64.msi on a Windows 7 Enterprise 64-bit laptop (17" hp ZBook).
Try to save any file.

Tried installing older versions:
mysql-workbench-community-6.2.4-win32.msi -- complains some file is missing, install fails
mysql-workbench-community-6.1.7-win32.msi -- installs, file save ok
mysql-workbench-community-6.0.9-win32.msi -- installs, file save ok
(and, happily, auto-saved scripts persist through all the uninstalls and installs!)

So my solution is to run 6.1.7 and give up on 6.2.4

Thank you for the bug report. The directories where you installed the tool or where you want to save the file have non English characters? (i.e. accented letters?). Thanks.

I installed all versions in the default locations proposed by the installer. The installation directory for the failing version 6.2 was:
C:\\Program Files\MySQL\MySQL Workbench 6.2 CE
which actually has fewer special characters than where the working version 6.1 installed itself:
C:\\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE

I didn't get as far as choosing a directory to save to. MySQL Workbench crashed before it got as far as prompting me for a location to save to. It crashed immediately after I clicked the floppy disk icon.

Thank you for the feedback. So the path Users\your_user_name\Documents doesn't has accented letters in your_user_name?. Thanks.

Right, no accented letters, no special characters even. My username is amitros. C:\Users\amitros\My Documents

Dear Ania and Miguel,
I confirm the problem persists in the new version 6.2.4.

After clicking on any save icon, the Worbench crashes and stop working. Really annoying!

I made a lot of things...
- I re-installed the application using administrative privileges (it didn't work).
- I removed the workbench folder located in C:\Users\my-user\AppData\Roaming\MySQL (it didn't work neither).
- I installed 6.2.3 (problem persisted).
- I installed all the windows update as of today (problem persisted).

The only solution, as indicated by Ania, was to install the version 6.1.7.

Thank you Ania.

Hope you can fix the problem as soon as possible.

Kind regards,

Héctor.

By the way. I'm using Windows 8.1 x64 on a Lenovo Twist.

I can confirm the new version 6.3.3.0 fixed the problem.

Please try version 6.3.3. Thanks.

That's what I said.
version 6.3.3 = 6.3.3.0 build 592
thks.

The feedback asked is for reporter Ania Mitros. Thanks.

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".

My logs files and a screenshot of wha it happening.

Attachment: log.zip (application/x-zip-compressed, text), 103.25 KiB.

I found the problem!

You have to have two monitors connected.

Steps to reproduce the problem:
1. Open MySQL Workbench
2. Move the opened window to the second screen monitor.
3. Connect to any database and make a query
4. Click to the save button
5. Workbench STOP WORKING!

Steps to avoid the problem:
1. Open MySQL Workbench
2. Move the opened window to the main screen monitor.
3. Connect to any database and make a query
4. Click to the save button
5. Save the file normally.
6. Now you can move the windows to the second screen monitor and workbench will work normally too.

Mine was crached when try to save in folder with greek letters in folder name. Renaming the folder using english chars resolved the problem

Please try version 6.3.4 with English characters in the path. Thanks.

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".

With 6.3.4 version (64 bits) on french version of windows 7 (64 bits) : 
- save in c:\modèle\ => crash
- save in c:\modele\ => ok

I'm running version 6.3.4 (x64) on Windows 10 SL, without strange chars in any path, with two monitors but in the main screen monitor. Whenever I push the save buttom for saving a model, workbench crashes. 
I have uninstalled and installed again Workbench and Redistributable C++ and the problem persists.
Also checked with version 6.2.5, the same occurs.
Even switching the application window between monitors, running queries or changing the model, the problem persists.
I have tried deactivating the second monitor (physically disconnected) and the problem persists.
I will try with version 6.3.3 as adviced...

Cesar, may you please open the workbench and switch between one screens before connecting to a specific database.

Sometimes, the workbench crashes in the second monitor, and some other times in the first time.

Perhaps may you please follow in detail these steps and let us know how it goes?

Steps to reproduce the problem:
1. Open MySQL Workbench
2. Move the opened window to the second screen monitor.
3. Connect to any database and make a query
4. Click to the save button
5. Workbench STOP WORKING!

Steps to avoid the problem:
1. Open MySQL Workbench
2. Move the opened window to the main screen monitor.
3. Connect to any database and make a query
4. Click to the save button
5. Save the file normally.
6. Now you can move the windows to the second screen monitor and workbench will work normally too.

Thanks Héctor, I tried both (steps to reproduce/avoid the problem) before and after connecting a database, with version 6.3.4 (64 bits) on Windows 10. 
The problem persists in every case.

Tried the same with version 6.3.4 (32 bits). The problem persists.

Tried with version 6.1.7 (32 bits). Problem solved!

Could not find version 6.3.3 for download, so I have not test this version.

Seems I will have to work with 6.1.7.  Thank you.

PLEASE URGENT FIX THIS ANNOYING BUG.

Several updates have passed and no fixes appear with regards this issue.

The problem is still persisting in the latest version and now I'm not able to avoid it. (even changing the window between monitors).

I'm being affected by this bug too. I'm using Workbench 6.3.5 Build 201 CE (64-bits) and the problem still exists. Please, fix this bug ASAP, it is not supposed to happen and it is very frustrating.

I'm running Windows 10 Home x64.

I have the same problem with Workbench 6.3.5 Build 201 CE (the same on both 32-bits and 64-bits version).  
I have now re-installed version 6.1.7.11891 build 1988 CE.  So far, everything seems to work as expected with this version.
I am running Windows 10 Pro 64-bit on 8GB machine.  
How can such an error exist for so long without being fixed?

I guess it's a problem of accent or something like that. I have downloaded the last version, saving the files to my drive or my other cloud is working good but first I tried to save into my primary cloud and it was also crashing. My url path is 96 char long and contain lower/uppercase and also numbers, spaces and some chars like '-' 'ô' 'é'

It's the first time I see a program crashing for those reasons. Usually it shows weird chars (or 8.3 chars for <1998 softs but crashing for this reason is weird and also weird this problem is still not fixed for a year now.

So I solved the issue but the problem is still there. I would always encounter this issue... I tested with my other cloud. Indeed it's the name. We should fix this issue while using no accent in the file or folder name but this issue must be fixed for having this thread closed. Because other people may encounter this...

Please try version 6.3.5.

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".