Bug #82466 Pressing 'delete selected rows' causes workbench to become unresponsive
Submitted: 5 Aug 2016 6:03 Modified: 25 Jan 2017 22:07
Reporter: Louis Persohn Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.3.7 OS:MacOS (Yosemite & El Capitan)
Assigned to: CPU Architecture:Any
Tags: delete selected rows, unresponsive

[5 Aug 2016 6:03] Louis Persohn 
Description:
Using the latest 6.3.7 client. When pressing 'delete selected rows' causes mysql workbench's CPU to spike; and the application becomes unresponsive. I have confirmed this issue on 4 mac os x laptops (El Capitan & Yosemite).

How to repeat:
Select the contents of a table; select * from blah.

Press the 'delete selected rows'

The application will stop responding.

Suggested fix:
'delete selected rows' should remove the row and await a commit/apply.
[5 Aug 2016 8:22] MySQL Verification Team 
Hello Louis,

Thank you for the report.
Verified as described with WB 6.3.7 on El Capitan.

Thanks,
Umesh
[19 Sep 2016 8:46] MySQL Verification Team 
Bug #83037 marked as duplicate of this one
[25 Jan 2017 22:07] Christine Cole 
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.9 release, and here's the changelog entry:

Deleting selected rows from the Result Grid caused MySQL Workbench to
become unresponsive.

Thank you for the bug report.
[15 Jan 2019 10:44] Mohamed Ahmed 
I am haveing the same problem with MySQL workbench 8.0.12
when i select multiple rows "huge number of rows" to delete the app hangs and it remain that way for minutes or hours depending on how many rows i choosed to delete.
i am working on windows 10 x64 with the following machine spec:
Xeon x5670 [12 Cores/24 Cache], RAM: 88 GB, x4 SAS [total of 60K RPM]

i never saw the app consume more than 500-600MB of RAM and 0.5 to 1.5 of the CPU even though as i stated i have planty of spare resources..

i will be glad to submit more info if you need any.