MySQL Bugs: #73067: workbench crash: error for object 0x8ad2c00: pointer being freed was not alloc

Bug #73067	workbench crash: error for object 0x8ad2c00: pointer being freed was not alloc
Submitted:	20 Jun 2014 17:37	Modified:	4 Jul 2014 11:09
Reporter:	Jacob Schwartz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	6.1.7	OS:	MacOS (10.9.3)
Assigned to:		CPU Architecture:	Any
Tags:	crash

Description:
The workbench crashes fairly regularly while executing SQL. It's usually while connected to a remote server via SSH tunnel. See the application crash dump, attached. An extract is included below.

Process:         MySQLWorkbench [1726]
Path:            /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier:      com.oracle.mysql.workbench
Version:         6.1.6 (1)
Code Type:       X86 (Native)
Parent Process:  launchd [279]
Responsible:     MySQLWorkbench [1726]
User ID:         501

Date/Time:       2014-06-20 12:21:32.531 -0500
OS Version:      Mac OS X 10.9.3 (13D65)
Report Version:  11
Anonymous UUID:  ECD9585C-1899-6B6F-A524-3823255C38EF

Crashed Thread:  21

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

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

How to repeat:
Not always repeatable but fairly regular (often a few times a day).

Open a connection to a remote database via SSH tunnel. Execute a select query. Boom.

Suggested fix:
Make it not crash

Workbench crash report

Attachment: mysql_workbench_crash_report.txt (text/plain), 81.47 KiB.

Please try version 6.1.7. Thanks.

I've downloaded 6.1.7 and I'll test throughout the next couple days.

Thank you please re-open this bug report when done.

I've been using the new version over the last few days and no crashes yet. Looking good so far! You're the best!

I'm happy to close and reopen if I see a recurrence?

Thank you for the feedback.