MySQL Bugs: #81966: crash with no log

Bug #81966	crash with no log
Submitted:	22 Jun 2016 8:07	Modified:	29 Jun 2016 7:40
Reporter:	V S	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	6.3.7	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
When a query is launched, it just crashes.
No warning, no error, no log.

It suddenly stopped working this week

How to repeat:
connect to a database, type a query, run it, crash

Which Linux version are you using?. Thanks.

Arch linux
4.6.2

I also get this issue on Windows 8.1 - but only when connected to MySQL 5.7 databases, not 5.6, 5.5 or 5.1

Thank you for the details.
This reminds me of Bug #81972, but cannot confirm since no back trace etc
I would suggest you to launch WB with --log-level=debug3 option and see if this helps. See https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html

OS X crash log

Attachment: workbench_6.3.7_crash.log (application/octet-stream, text), 25.97 KiB.

See my attached crash log above ^^^

Trimmed crash report from OS X, main culprit "pointer being freed was not allocated".

Its intermittent, I can start the app run the query, works, wait awhile connect to another DB run a query, crash. Restart run a query, crash, restart run the same query, works. Besides a missing null check, its like a timer/thread event isn't done allocating before a dealloc happens.

Thank you for the feedback.
Observed this with WB 6.3.7 on OS X 10.11.x El Capitan

Same. Connected via SSH tunnel, workbench 8.0.22, server 5.7.26

Attachment: workbench_8.0.22.log (text/x-log), 8.13 KiB.

Same. Linux Mint 19.3 Tricia. Connected via SSH tunnel, workbench 8.0.22, server 5.7.26

Attachment: workbench_8.0.22.log (text/x-log), 8.13 KiB.