Bug #79726 | Workbench crashes Opening non-image BLOB Value in Editor. | ||
---|---|---|---|
Submitted: | 22 Dec 2015 0:26 | Modified: | 23 Dec 2015 2:48 |
Reporter: | IT Services | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 6.2.4 | OS: | Windows (Microsoft Windows 7 Professional Service Pack 1) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[22 Dec 2015 0:26]
IT Services
[22 Dec 2015 5:32]
MySQL Verification Team
Hello! Thank you for the report. I'm seeing this issue with 6.2.4 and with provided steps but no longer seeing the crash with the same steps on latest WB 6.3.6. Could you please try and confirm the same? Thanks, Umesh
[22 Dec 2015 5:34]
MySQL Verification Team
Also, https://bugs.mysql.com/bug.php?id=75516
[23 Dec 2015 2:48]
IT Services
Umesh I can confirm that problem I reported no longer happens in WB 6.3.6 But let me make couple related comments. 1. WB 6.2.4 Help > "Check for Updates" was telling me that it was still the latest version. 2. WB 6.3.6 now rendered a number of my connections unusable. Attempting to connect I get: "SSL connection error: protocol version mismatch". That's despite having set option "Use SSL" to NO. Server instances (MySQL 5.5.35) report variables have_openssl and have_ssl = YES but have expired certificates. Version 6.2.4 has no problem communicating with these servers. I suppose I may/should turn second point into a new bug report as I have not been able to find anyone reporting this as yet as a problem. Again, as for the original problem - it is resolved with WB 6.3.6 and this bug report can be closed. Thank you for your assistance.