Bug #78881 | Stopping a query causes Workbench to crash | ||
---|---|---|---|
Submitted: | 20 Oct 2015 10:35 | Modified: | 21 Jan 2017 21:28 |
Reporter: | Kassian Ortner | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 6.3.4 | OS: | Windows (Microsoft Windows 10 Pro) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[20 Oct 2015 10:35]
Kassian Ortner
[20 Oct 2015 11:23]
MySQL Verification Team
Crash message
Attachment: long_query.png (image/png, text), 28.28 KiB.
[20 Oct 2015 11:23]
MySQL Verification Team
Thank you for the bug report.
[13 Jan 2016 17:29]
Caleb Begly
I can confirm that this happens locally with both long queries (with small number of results) and large result sets. However, going to the mysql command line outside of workbench and terminating the query safely terminates it for workbench.
[13 Jan 2016 17:33]
Caleb Begly
Information from the event log: Faulting application name: MySQLWorkbench.exe, version: 6.2.4.12437, time stamp: 0x5462a5c4 Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff Exception code: 0xc0000417 Fault offset: 0x000000000006dd3d Faulting process id: 0x2824 Faulting application start time: 0x01d14e176761be01 Faulting application path: C:\Program Files\MySQL\MySQL Workbench 6.2 CE\MySQLWorkbench.exe Faulting module path: C:\Windows\system32\MSVCR120.dll Report Id: 0db2c8ee-ba0d-11e5-991d-4ceb427e38cb XML Details: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-01-13T15:48:14.000000000Z" /> <EventRecordID>47809</EventRecordID> <Channel>Application</Channel> <Computer><REDACTED></Computer> <Security /> </System> - <EventData> <Data>MySQLWorkbench.exe</Data> <Data>6.2.4.12437</Data> <Data>5462a5c4</Data> <Data>MSVCR120.dll</Data> <Data>12.0.21005.1</Data> <Data>524f83ff</Data> <Data>c0000417</Data> <Data>000000000006dd3d</Data> <Data>2824</Data> <Data>01d14e176761be01</Data> <Data>C:\Program Files\MySQL\MySQL Workbench 6.2 CE\MySQLWorkbench.exe</Data> <Data>C:\Windows\system32\MSVCR120.dll</Data> <Data>0db2c8ee-ba0d-11e5-991d-4ceb427e38cb</Data> </EventData> </Event>
[12 May 2016 11:54]
Andrea Turso
This report also applies to MySQLWorkBench 6.5 b511 CE on Mac. Stopping a query causes the program to hang and become unresponsive. In my particular case this issue is more frequent when the connecting to a database over SSH, although it still happens with local databases from time to time.
[21 Jan 2017 21:28]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Workbench 6.3.9 release, and here's the changelog entry: Stopping a query before it finished executing often caused MySQL Workbench to stop working. Thank you for the bug report.