Bug #76362 Copying previous SQL statement from History panel locks up / crashes Workbench
Submitted: 17 Mar 2015 23:42 Modified: 27 Mar 2015 1:29
Reporter: Mike Reid Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:6.3.2 OS:MacOS (10.10.2)
Assigned to: CPU Architecture:Any
Tags: copy, crash, history, sql editor, workbench

[17 Mar 2015 23:42] Mike Reid 
Description:
Any time I attempt to copy a previous SQL statement from the history panel in the SQL Editor, Workbench completely locks up and immediately crashes.

How to repeat:
1. Connect to a database server you've previously run SQL commands against (in my case, year's worth varying across many versions of Workbench)

2. Change "Action Output" to "History" in the panel below the SQL Editor

3. Highlight any previous statement's row

4. Right-click and select "Copy Row" from the context menu

5. Watch as Workbench completely locks up and crashes, requiring app relaunch.

Suggested fix:
Prevent unnecessary crashing when copying historical SQL statements.
[18 Mar 2015 0:18] MySQL Verification Team 
Out of Memory

Attachment: out_of_memory.png (image/png, text), 129.60 KiB.
[18 Mar 2015 0:19] MySQL Verification Team 
Thank you for the bug report.
[27 Mar 2015 1:29] Philip Olson 
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.3 release, and here's the changelog entry:

Copying SQL statements from the history panel would crash MySQL Workbench.

Thank you for the bug report.