| Bug #94070 | MySQL Workbench 8.0.14 crash Windows 10/64-bit | ||
|---|---|---|---|
| Submitted: | 25 Jan 2019 22:00 | Modified: | 3 Oct 2019 17:08 |
| Reporter: | Glenn Shepherd | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S2 (Serious) |
| Version: | 8.0.14 | OS: | Windows (Windows 10) |
| Assigned to: | CPU Architecture: | x86 (Core i7 64-bit) | |
| Tags: | crash, workbench | ||
[25 Jan 2019 22:00]
Glenn Shepherd
[28 Jan 2019 7:29]
MySQL Verification Team
I could not repeat this issue on my side, one laptop and one desktop, please try tocheck and install if needed the Microsoft visual c++ 2017 redistributable package and re-install WorkBench wit repair option. Thanks.
[11 Feb 2019 16:31]
Glenn Shepherd
-- Attempted Repair as requested. No change.
-- 2/11/2019 - Installed 8.0.15 - Upgrade completed successfully.
-- No change in Application crash. References to Workbench/Python27.dll appear to include Framework version v4.0.30319?
-- Visual Studio with Framework SDK 4.5.1, 4.5.2 & 4.7.2 Targeting, resident on system.
-- Fr
<Provider Name=".NET Runtime" />
<Data>Application: MySQLWorkbench.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at <Module>.wb.WBContextUI.init(wb.WBContextUI*, wb.WBFrontendCallbacks*, wb.WBOptions*)
at MySQL.Workbench.WbContext.init(MySQL.Workbench.WbFrontendCallbacks, MySQL.Workbench.WbOptions, VoidStrUIFormDelegate)
at MySQL.GUI.Workbench.Program.Main(System.String[])
<EventData>
<Data>MySQLWorkbench.exe</Data>
<Data>8.0.15.0</Data>
<Data>5c51b69e</Data>
<Data>python27.dll</Data>
<Data>2.7.14150.1013</Data>
<Data>5b970235</Data>
<Data>c0000005</Data>
<Data>00000000000e2634</Data>
<Data>28c4</Data>
<Data>01d4c21df1745ed9</Data>
<Data>C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe</Data>
<Data>C:\Program Files\MySQL\MySQL Workbench 8.0 CE\python27.dll</Data>
<Data>7ff97a3c-7f9e-435c-8e3f-e81f04700ec3</Data>
</EventData>
[17 Feb 2019 19:26]
Glenn Shepherd
Workaround -- Run as (any) other Windows user profile. However: Why would this report as 'corrupt memory' / fatal error?
[13 Mar 2019 18:32]
Boris Gligich
same in 8.0.15, and work around doesn't work if you don't have any other profiles
[15 May 2019 8:30]
Janne Lepola
I tried installing "export-laravel-5-migrations.py" file vie scripting -> install plugin/module, but I had accidentally saved this file from github as html-file (instead of opening the raw-file). I didn't get any errors, but after trying to restart I started getting this "wb.WBContextUI.init(WBContextUI ..." -error. Reinstalling Workbench didn't help, but after deleting workbench configuration folder from C:\users\*username*\AppData\Roaming\ it started working without hickup. Apparently malfuncted python-scripts can result to workbench not booting, so I would suggest to add validation either to install-phase or handle the error during boot.
[3 Sep 2019 17:08]
MySQL Verification Team
Try what Janne did: deleting workbench configuration folder from C:\users\*username*\AppData\Roaming\ .
[4 Oct 2019 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".
[29 Jan 2020 5:36]
Sushant Rath
Event Log:- Application: MySQLWorkbench.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException at MySQL.GUI.Workbench.Program.Main(System.String[]) Faulting application name: MySQLWorkbench.exe, version: 8.0.19.0, time stamp: 0x5df6944b Faulting module name: KERNELBASE.dll, version: 10.0.18362.535, time stamp: 0x50cc8d5a Exception code: 0xe0434352 Fault offset: 0x000000000003a839 Faulting process id: 0x2e30 Faulting application start time: 0x01d5d506f35a1140 Faulting application path: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 9d6a5c33-0b7a-4a8c-9583-a7ee07fdf012 Faulting package full name: Faulting package-relative application ID: Tried Suggested solution:- Deleted the Workbench File from C:\Users\"userName"\AppData\Roaming\MySQL Restarted the system, but no difference.
[20 Feb 2020 17:04]
David VanWormer
Tried removing folder as mentioned above. Did not help. Also getting: Application: MySQLWorkbench.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException at MySQL.GUI.Workbench.Program.Main(System.String[]) Faulting application name: MySQLWorkbench.exe, version: 8.0.19.0, time stamp: 0x5df6944b Faulting module name: KERNELBASE.dll, version: 10.0.18362.628, time stamp: 0xf96f12ee Exception code: 0xe0434352 Fault offset: 0x000000000003a839 Faulting process id: 0xe78 Faulting application start time: 0x01d5e80ec842a77b Faulting application path: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 92e8dfe3-f936-43a2-ae56-029e5d852622 Faulting package full name: Faulting package-relative application ID:
[27 Mar 2020 12:50]
Михаил ько
Just install Redist 2015 2017 2019 I solved by install https://support.microsoft.com/ru-ru/help/2977003/the-latest-supported-visual-c-downloads
