MySQL Bugs: #82231: Crash when executing query SSH

Bug #82231	Crash when executing query SSH
Submitted:	14 Jul 2016 14:53	Modified:	7 Mar 2017 23:08
Reporter:	Jon Andersen	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	6.3.7	OS:	MacOS
Assigned to:		CPU Architecture:	Any

Description:
MySQL Workbench crashes very frequently whenever I try to run a query. I'm currently using SSH to access the. 

How to repeat:
Connect to server over SSH
Run a query (crashes 50% of the time)

Crash report

Attachment: crash.txt (text/plain), 95.01 KiB.

Bug #82532 marked as duplicate of this

I have the same issue. 

Model: MacBookPro11,4, BootROM MBP114.0172.B09, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 2.29f24
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x152), Broadcom BCM43xx 1.0 (7.21.95.175.1a6)
Bluetooth: Version 4.4.4f4 17685, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Network Service: GHP, IPSec, utun0
Serial ATA Device: APPLE SSD SM0256G, 251 GB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1

Process:               MySQLWorkbench [42573]
Path:                  /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier:            com.oracle.mysql.workbench
Version:               6.3.7.CE (1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           MySQLWorkbench [42573]
User ID:               501

Date/Time:             2016-08-10 14:02:55.056 -0500
OS Version:            Mac OS X 10.11.4 (15E65)
Report Version:        11
Anonymous UUID:        D915CAD4-FF13-4CE0-8282-67A1F6649AEC

Sleep/Wake UUID:       717EC3C0-0CDE-458F-9B6B-25F97AE0D901

Time Awake Since Boot: 1100000 seconds
Time Since Wake:       500 seconds

System Integrity Protection: enabled

Crashed Thread:        20

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called
*** error for object 0x7fd915953e00: pointer being freed was not allocated

http://bugs.mysql.com/bug.php?id=82578 marked as duplicate of this one.

http://bugs.mysql.com/bug.php?id=83337 marked as duplicate of this one.

Please try version 6.3.8. Thanks.

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".

This is still an issues in 6.3.8

Please try version 6.3.9. Thanks.

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".

The last helpful suggestion in this thread was to try 6.3.9, which no one has responded to, so the bug is suspended. I'll bump the thread by saying that I've upgraded to 6.3.9 and it still crashes several times per day, sometimes even just after freshly opening the tool. This issue has been around for almost a year now, can we get some movement on it besides the usual poke-and-hope?

Thanks

I am also still suffering from this, as are colleagues of mine, on 6.3.9 (10690321 CE 64bit), running on Windows 8.1 Pro x64.  It's becoming a bad joke now.  Start MySQL twice - once to connect to the database and crash on the first query, and then the second time to actually run your queries.

For what it's worth, my experience is that the crash happens:
1. On first opening the connection, and 
2. When coming back to a MySQL workbench window (which has been open for a while) and trying to execute the first query after a period of inactivity.

I have found that once I have a window open and am able to execute the first query, then I can continue writing and executing queries at regular intervals with no issue.