MySQL Bugs: #76078: Stopping a query causes Workbench to crash

Bug #76078	Stopping a query causes Workbench to crash
Submitted:	27 Feb 2015 13:20	Modified:	21 Oct 2015 10:07
Reporter:	Jonathan Corwin	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	6.2.4	OS:	Windows (Microsoft Windows 8.1 Pro)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\jonathan.corwin\AppData\Roaming\MySQL\Workbench\log\wb.log]

If I click the "Stop the query being executed" when a query is running, Workbench crashes. Sometimes the first click doesn't do anything and I have to click it again.

How to repeat:
Click the "Stop the query being executed" when a query is running.

Suggested fix:
Stop Workbench crashing when the "Stop the query being executed" button is clicked.

Query Cancelled output

Attachment: query_cancelled.png (image/png, text), 36.81 KiB.

I couldn't repeat (see prior attached picture with the expected action) retrieving a large result set. Please give more details how to repeat the issue. My environment is:

MySQL Workbench Community (GPL) for Windows version 6.2.4  revision 12437 build 2426 (64 bit)
Configuration Directory: C:\Users\Miguel\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files\MySQL\MySQL Workbench 6.2 CE
Cairo Version: 1.10.2
OS: Microsoft Windows 8.1 Pro
CPU: 8x Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz, 16.0 GiB RAM
Active video adapter NVIDIA GeForce GT 720
Installed video RAM: 1024 MB
Current video mode: 3840 x 2160 x 4294967296 colors
Used bit depth: 32
Driver version: 9.18.13.4725
Installed display drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Current user language: Portuguese (Brazil)

A bit of further experimentation with some simpler queries and I couldn't reproduce. 
However I have tried it with a fabricated query of:

SELECT * FROM myverybigtable
INNER JOIN (SELECT * FROM myverybigtable) x

This would take a significant amount of time to run if I left it.

Workbench shows "Running..." with duration/fetch "? / ?" at the point when it crashes.
Looking at the processlist, the query was in a stage of Query / "Copying to tmp table"

Client out of memory

Attachment: out_of_memory.png (image/png, text), 33.51 KiB.

Thank you for the feedback. I still not able to repeat when I ran a query like you provide which creates a large dataset I got a message that the client ran out of memory and the query stop button interrupt the query.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Making this one duplicate of http://bugs.mysql.com/bug.php?id=78881 which was verified.

Greetings, i've got two connections to two different databases. 
one of them works just fine,
the other one when i run a query windows curshes the application for no actual reason.