Bug #60588 Workbench crashes displaying some binary data
Submitted: 22 Mar 2011 13:40 Modified: 18 May 2011 2:20
Reporter: Andrew Feren Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:<= 5.2.33 OS:Linux (Ubuntu 10.04)
Assigned to: CPU Architecture:Any

[22 Mar 2011 13:40] Andrew Feren
Description:
Selecting from a table that has certain data in a VARBINARY column will crash workbench.

Not all binary data will crash workbench when selected.   Not sure what the magic pattern is.  I will attach a file with a selection of rows that will crash workbench as well as some rows that won't cause a crash.

Only tested on Linux.  May also occur on other platforms.

How to repeat:
SELECT * FROM table_with_bad_binary;

or right click on the table in the schema view and select 
"Select Rows - Limit 1000"
[22 Mar 2011 13:41] Andrew Feren
Dump of table that crashes Workbench

Attachment: Dump20110322.sql (text/x-sql), 8.40 KiB.

[22 Mar 2011 13:44] Andrew Feren
In my attached dump file, the rows that will cause a crash are data_ids 938, 2001, 2003, 2102, 2103,2104,and 2105

-- This will work
SELECT * FROM temp.bin_data where data_id NOT IN (938, 2001, 2003, 2102, 2103,2104,2105);

-- This will crash
SELECT * FROM temp.bin_data where data_id IN (938, 2001, 2003, 2102, 2103,2104,2105);
[18 May 2011 2:20] Paul DuBois
Noted in 5.2.34 changelog.

Workbench could crash trying to display result sets that contained
binary data.