Bug #71327 Workbench crash on drop schema with open transaction
Submitted: 9 Jan 2014 14:19 Modified: 8 Feb 2014 2:35
Reporter: Thomas Brown Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:Workbench CE 6.0.8 OS:Windows (7 Ultimate SP 1)
Assigned to: CPU Architecture:Any
Tags: crash, drop schema, workbench

[9 Jan 2014 14:19] Thomas Brown 
Description:
The workbench crashes when trying to drop a schema that has a non committed or reverted transaction.

If it's relevant the MySQL DB being connected to is version '5.6.15-log'. Also the schema being dropped is 840MB when it's exported using the 'Data Export' tool.

How to repeat:
- Turn off auto commit mode
- Insert into a table
- Under the 'SCHEMAS' right-click the schema you did an insert in and click 'Drop Schema...'
- Workbench waits for a little while then Windows complains that it's not responding
[9 Jan 2014 14:53] MySQL Verification Team 
Hello Thomas,

Thank you for the report.
Verified as described.

Thanks,
Umesh
[8 Feb 2014 2:35] Philip Olson 
Fixed as of the upcoming MySQL Workbench 6.1.2 release, and here's the changelog entry:

Dropping a schema that had non-committed or reverted transactions could
crash MySQL Workbench, but now the drop statement is executed as a user
command so it can be aborted.

Thank you for the bug report.