Bug #120006 Workbench crashes with assertion failed on running queries

• Submitted: 8 Mar 14:03
• Reporter: Dagh Bunnstad
• Status: Won't Fix
• Category: MySQL Workbench
• Severity: S2 (Serious)
• Version: 8.0.38
• OS: Windows (Windows 11 Pro 25H2 26200.7462)
• CPU Architecture: x86 (11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz (3.60 GHz))

[8 Mar 14:03] Dagh Bunnstad

Description:
Workbench crashes with assertion error when executing queries.
This error has been around for years by now, how about you check it out?

Related to 113459 but no-one is responding there.

Workspace log shows query was executed:
[75, 14:34:22] update ...: 182 row(s) affected
Rows matched: 182  Changed: 182  Warnings: 0

wb.log contains nothing of importance at crash.

Error is:

---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Assertion failed!

Program: ...Files\MySQL\MySQL Workbench 8.0 CE\wbpublic.be.dll
File: C:\build\sb_1-15882819-1718583859.9...\forced_...urn.hpp
Line: 38

Expression: false

For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts

(Press Retry to debug the application - JIT must be enabled)
---------------------------
Abort   Retry   Ignore   
---------------------------

How to repeat:
Intermittent, if anything is to go by it's caused by having Workbench open for a long time and making a query, possibly after having lost connection to the server. At which point the query will be executed (can be seen if output window is open, and changes will persist), but crashes immediately after that, if it was a select query, no data is displayed in GUI.

Suggested fix:
Fix the (cause of the) assertion error.

[14 Sep 18:07] Omer Barnir

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.