Bug #113459 Assertionfailed! wbpublic.be.dll
Submitted: 19 Dec 2023 10:09 Modified: 4 Jan 2024 10:24
Reporter: Danny Casier Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0.34 build 3263449 CE 64 OS:Windows (windows sever 2022 stand)
Assigned to: CPU Architecture:Any
Tags: wbpublic.be.dll

[19 Dec 2023 10:09] Danny Casier
Description:
After working a long time suddly MWB freezes and gives sometimes an error (not always) After clicking one of the buttons it stops. In case there was no warning it stops. It is always when a query is started to executing.
After restarting MWB and reconnecting sometimes all scripts are lost.

This is a bug that excists since many years when i look in the bug list. This is very annoying. This is realy needed to solved.

Error popup shows: 
Microsoft Visual C++ Runtime Library 
Assertion failed! 
program: ...am Files\MySQL\MySQL Workbench
8.0\wbpublic.be.dll 
File:C:\buildsb_1-12054853-1689254918.0\forced_...urn.hpp 
Line: 38 
Expression: false 
For information on hou your program can cause an assertion 
failure, see the Visual ++ documentation on asserts 

In the MS events :
Faulting application name: MySQLWorkbench.exe, version: 8.0.34.0, time stamp: 0x64affe0e
Faulting module name: ucrtbase.dll, version: 10.0.20348.1, time stamp: 0xdacb234c
Exception code: 0x80000003
Fault offset: 0x000000000007d9bc
Faulting process id: 0xf24
Faulting application start time: 0x01da2f6a68245fce
Faulting application path: C:\Program Files\MySQL\MySQL Workbench 8.0\MySQLWorkbench.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: d2146454-fb92-47ec-95d3-0a4fad61e7d5
Faulting package full name: 
Faulting package-relative application ID: 

Fault bucket 2089739556361198503, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MySQLWorkbench.exe
P2: 8.0.34.0
P3: 64affe0e
P4: ucrtbase.dll
P5: 10.0.20348.1
P6: dacb234c
P7: 80000003
P8: 000000000007d9bc
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1151b67c-391a-4540-b870-0bb552647d66.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bd0f7005-7bef-4e06-acd0-94dc83a7cfcb.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0eca2cd7-65a2-4255-9612-821a7b4c85e2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7b8685aa-0677-4db5-bb39-fb3565475ad6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.de091ce2-b8dc-4aab-833e-3642bd52265b.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MySQLWorkbench.e_75ffe6be2ba6f53c3828b6e81d47f3950a5d3fa_e1b41f7a_cea7fa84-ec0a-46c0-91c3-dc0ba7f56f0e

Analysis symbol: 
Rechecking for solution: 0
Report Id: d2146454-fb92-47ec-95d3-0a4fad61e7d5
Report Status: 268435456
Hashed bucket: d87902a795a2acdcbd003f0df9fddba7
Cab Guid: 0

How to repeat:
After working for many years and having that specific many many times I can just say it appears when executing a query.

Suggested fix:
Perhaps it has something to do when the execute command is given at the same time the auto save was running.
[19 Dec 2023 12:54] MySQL Verification Team
Hello Danny Casier,

Thank you for the bug report.
I tried to reproduce your issue on windows 11 with workbench 8.0.34 but I am not seeing any issues at my end. If you can provide more information, feel free to add it to this bug. Thanks.

Regards,
Ashwini Patil
[4 Jan 2024 10:24] Danny Casier
Is freeze up in many situations.
I'm using it via RDP and normaly do not closed when I disconnect the rdp.
I'm using WB connected to serveral SQL servers at once.
It appears only when I execute a querie. It gives a waiting cursor and after a few seconds it freeze up. Then after a while WB close whitout reason.
Somtimes I can work days without problems. And somtimes I have that sympton more times in a day. It has nothing to do with the querie self. It appears even with a very short querie on a litle tabel.
[11 Feb 2024 11:47] Dagh Bunnstad
Having the same or very similar problem and the same thing has been happening for years (though could be several different errors), if it wasn't for the fact that Workbench is good otherwise I would have changed years ago. All I ever see about these problems is that someone reports them and that you can't replicate them, and then the issue is closed, as if that means that they don't exist.

It always happens when executing a query, or rather the query always (at least from what I remember) gets executed but it seems that something happens when Workbench is trying to present the result as that's when it's crashing. I even get a log entry in the action output window saying that the query has executed and the rows affected/returned reported.

Pretty much always running connection with TCP/IP over SSH, if that's important.

Windows 11 Pro 22H2
MySQL Workbench 8.0.33.0 build 2947366 CE (64 bits)

Error dialog is:
---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Assertion failed!

Program: ...Files\MySQL\MySQL Workbench 8.0 CE\wbpublic.be.dll
File: C:\build\sb_1-10901159-1679672384.7...\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   
---------------------------
[17 Mar 2024 11:37] Dagh Bunnstad
It has happened a few more times since last reported, always the same error.

If it just popped up an error message saying that it couldn't render the result, or whatever the problem is, it would be okay, but as it is it terminates the application.
[13 Nov 2024 13:53] Dagh Bunnstad
Still happens in 8.0.40:

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

---

Faulting application name: MySQLWorkbench.exe, version: 8.0.38.0, time stamp: 0x666f83ae
Faulting module name: wbpublic.be.dll, version: 0.0.0.0, time stamp: 0x666f830c
Exception code: 0x80000003
Fault offset: 0x000000000000d9ee
Faulting process id: 0x0x61B8
Faulting application start time: 0x0x1DB18993F0C1C75
Faulting application path: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe
Faulting module path: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\wbpublic.be.dll
Report Id: 08bf5896-a12b-49b8-b97b-48beeb7995be
Faulting package full name: 
Faulting package-relative application ID: