Bug #110787 When quitting MySQL Workbench get error message about workbench unexpectedly qui
Submitted: 24 Apr 2023 17:05 Modified: 26 May 2023 12:50
Reporter: Harry Towner Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S5 (Performance)
Version:8.0.33 OS:MacOS (13.3.3)
Assigned to: CPU Architecture:ARM

[24 Apr 2023 17:05] Harry Towner
Description:
When you quit MySQL Workbench a pop-up window appears stating that MySQL Workbench unexpectedly quit wit ha very long dump. This happens every time.

How to repeat:
This happens every time.
[25 Apr 2023 12:51] MySQL Verification Team
Hello Harry Towner,

Thank you for the bug report.
Could you please provide the dump file?

Regards,
Ashwini Patil
[4 May 2023 21:13] Darren Oh
Dump file

Attachment: MySQLWorkbench-2023-05-04-171045.ips (application/octet-stream, text), 36.27 KiB.

[11 May 2023 14:30] Angelo Severgnini
any updates on this? i'm experiencing same problem here
[14 May 2023 20:32] Martin Frost
crash-on-quit-macos-arm

Attachment: MySQLWorkbench-2023-05-14-213028.ips (application/octet-stream, text), 34.14 KiB.

[26 May 2023 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[26 May 2023 8:49] Martin Frost
Recent crash log

Attachment: MySQLWorkbench-2023-05-26-094624.ips (application/octet-stream, text), 35.65 KiB.

[26 May 2023 12:04] Angelo Severgnini
'No feedback was provided for this bug for over a month...'

are you kidding? there are a lot of feedback here...
is there anyone working on this fix?????
[26 May 2023 12:50] MySQL Verification Team
Hello,

Thank you for the feedback.
Imho this is duplicate of Bug #110613, please see Bug #110613.

Regards,
Ashwini Patil
[26 May 2023 13:14] Angelo Severgnini
not sure why, but i don't have access to this bug #110613
[26 May 2023 13:56] Darren Oh
Similar issues in the last release were fixed in the current release, but I have not seen any duplicates of this bug. This bug is in the latest release.