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: | |
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
[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.