Bug #81480 mysql workbench crash when executing SQL statements

• Submitted: 18 May 2016 9:08
• Modified: 14 Jun 2018 20:40
• Reporter: chen taosheng
• Status: Closed
• Category: MySQL Workbench
• Severity: S1 (Critical)
• Version: 6.3.6, 6.3.5, 6.2.5
• OS: Windows (7 x64)
• CPU Architecture: Any
• Tags: crash

[18 May 2016 9:08] chen taosheng

Description:
mysql workbench crash when executing SQL statements in two connections at the same time.

call stack:
------------------------------------------------
msvcr120.dll!__crt_debugger_hook(int _Reserved) Line 60	C
msvcr120.dll!_call_reportfault(int nDbgHookCode, unsigned long dwExceptionCode, unsigned long dwExceptionFlags) Line 208	C++
msvcr120.dll!_invoke_watson(const wchar_t * pszExpression, const wchar_t * pszFunction, const wchar_t * pszFile, unsigned int nLine, unsigned __int64 pReserved) Line 138	C++
msvcr120.dll!_invalid_parameter(const wchar_t * pszExpression, const wchar_t * pszFunction, const wchar_t * pszFile, unsigned int nLine, unsigned __int64 pReserved) Line 85	C++
msvcr120.dll!_invalid_parameter_noinfo() Line 97	C++
msvcr120.dll!fprintf(_iobuf * str, const char * format, ...) Line 55	C
wbprivate.be.dll!000007fed06396ed()	Unknown
wbprivate.be.dll!000007fed0697b1a()	Unknown
wbprivate.be.dll!000007fed06af5f6()	Unknown
wbprivate.be.dll!000007fed06aef32()	Unknown
wbprivate.be.dll!000007fed06ae1bc()	Unknown
wbprivate.be.dll!000007fed06ab338()	Unknown
wbpublic.be.dll!000007fecd605219()	Unknown
wbpublic.be.dll!000007fecd60516e()	Unknown
wbpublic.be.dll!000007fecd5e96a9()	Unknown
wbpublic.be.dll!000007fecd5e7183()	Unknown
wbpublic.be.dll!000007fecd5e9127()	Unknown
wbpublic.be.dll!000007fecd5e8396()	Unknown
libglib-2.0-0.dll!0000000068627881()	Unknown

How to repeat:
1. open two connections.
2. begin to execute 1000 insert statements
3. switch to another connection
4. execute 1000 insert statements

[18 May 2016 11:54] MySQL Verification Team

Hello chen taosheng,

Thank you for the report.
Observed this on Win7 with WB 6.3.6.

Thanks,
Umesh

[14 Jun 2018 20:40] Christine Cole

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.12 release, and here's the changelog entry:

Executing separate queries (each in its own connection tab) caused MySQL
Workbench to exit.

Thank you for the bug report.