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: | |
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
[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: