MySQL Bugs: #84745: MySQL Workbench - Internal error when connecting to MySQL

Bug #84745	MySQL Workbench - Internal error when connecting to MySQL
Submitted:	31 Jan 2017 15:57	Modified:	7 Mar 2017 23:06
Reporter:	Tomek Marecki	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	6.3.8	OS:	Ubuntu
Assigned to:		CPU Architecture:	Any

Description:
Hi,
I am running MySQL Workbench 6.3, build 1228 CE (64 bits) on Ubuntu 16.04 LTS.
When I connect to one of my databases (MySQL 5.7) it crashes, giving the error box:
"Exception caught while processing action from home screen: basic_filebuf::underflow invalid byte sequence in file: iostream error"

When I create a new connection it works fine, however I can't reopen the existing one. It might be due to corrupted "queries tab" data related to that connection. MySQL Workbench fairly often tend to crash for me when running a SELECT statement.
It happens not frequent enough to find any pattern, sometimes it crashes, next time doing exactly same steps, it doesn't crash.

How to repeat:
No idea when it happens exactly

error window

Attachment: workbench_crash.png (image/png, text), 186.10 KiB.

Thank you for the bug report. Which kind of connection are you using (ssh, local, remote)?. Thanks.

This happens when I connect to the remote resource (no SSH used, not local).

Please try version 6.3.9. 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".

I'm experiencing the same issue on Ubuntu 17.04 amd64 with Mysql Workbench 6.3.8

I found this ticket, so I tried what you asked to try, I installed mysql-workbench-community 6.3.9

I'm experiencing the same error

(mysql-workbench-bin:25239): glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: basic_filebuf::underflow invalid byte sequence in file: iostream error

For records, I'm trying to access a remote database via an SSH tunnel.

I noticed that, I'm only experiencing the issue on some servers.

I don't know if this will help you but

it works on :
- one server 5.6.36-82.0-log Percona Server (GPL), Release 82.0, Revision 58e846a
- on server 5.7.18-15-log Percona Server (GPL), Release '15', Revision 'bff2cd9'

but not on :
- on server 5.6.36-82.0-56 Percona XtraDB Cluster (GPL), Release rel82.0, Revision de7a681, WSREP version 26.20, wsrep_26.20

- on server 5.6.36-82.0-56 Percona XtraDB Cluster (GPL), Release rel82.0, Revision de7a681, WSREP version 26.20, wsrep_26.20

The ones that are not working have 20+ "auto saved" tab of queries.

I tried to delete and recreate the connection, and it worked.