MySQL Workbench crashes on mac os (fresh install) - mysql-workbench

I installed mySQL workbench and I can't open it, it crashes right away.
SQL is installed, I can access databases in my terminal.
The sql server is running.
Im on mac os 11.1
I researched this topic, I found that a plugin can cause this, but I don't even have that plugin in my files.
Time Awake Since Boot: 890 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Abort trap: 6
Termination Reason: Namespace SIGNAL, Code 0x6
Thanks in advance if you could help!

MySQLWorkbench 8.0.23 crashes for me on startup on macOS 11.1, but downgrading to 8.0.22 from MySQL archives allows it to startup without a problem.
This bug is reported to the MySQL bug tracker: https://bugs.mysql.com/bug.php?id=102284

I was having the exact same issue, I was able to download the older version from MySql's archives, and it worked for me.
P.S., I also had to go into System Preferences > Security & Privacy > General and open anyway for MySQL.

I was having this crash issue on my mac Monterey 12.3 with the latest Mysql workbench 8.0.31, So I uninstalled it and did a fresh install of lower version 8.0.27. And it is working fine now.

As many people suggested, downloading and using the previous version may help resolve the issue. I encountered an error while using version 8.0.31, so I downloaded version 8.0.30 and to my surprise, the problem was fixed.

I had the same problem (macOS BigSur 11.6.3) : could not upgrade to any v8.x version.
After further investigation, I found that I was having a user module (script I wrote several years ago to generate automatic documentation).
After removing it from the 6.3 version (menu : Scripting > Scripting shells > Files > User module) I was able to install and run MysqlWorkbench 8 (8.28 for instance)

Related

MySQL Workbench 8.0.32.CE crashes on macOS Monterey 12.6.3

This happens to me when I run the show databases commands; and the SHOW CREATE TABLE command.
The other commands I can write and execute normally.
MacBook Pro early 2015, 64 bits.
I tried to check the MySQL version (x86_64 Homebrew install), I tried to restart the processes.
I was also having the same issue where if I ran any type of query the entire application would crash, v8.0.31 seems to be the most stable version and that worked for me.
I was also facing the similar problem with 8.0.32, but I tried with 8.0.30 and my problem got resolved. So you can try with lesser version 8.0.30 or equal.

MongoDB Compass loading forever

My MongoDB Compass won't launch. It was working an hour ago, but now it just shows this screen forever.
I've tried rebooting. And even uninstalling and re-installing Compass. But every time I launch it, it just shows the loading screen and never proceeds. If I go to Connect > Connect to..., it just opens another window that does the same thing.
Version 1.10.9
Windows 10 x64
How can I get this program to launch correctly? What should I investigate to try to figure this out?
Had the same issue today, with the Version 1.10.9 on Mac OSX. I then reinstalled MongoDB Compass Community Edition to the latest Beta version (Version 1.11.0-beta.1), the loading proceeded and everything went fine.
Same here. I tried uninstalling/reinstalling. No joy.
I reinstalled an older version 1.8.2 which worked fine. Must be an issue with the latest release.
Edit: I upgraded to 1.10.9 this morning and reverted to 1.8.2 after coming across this issue.
After having the same issue today (november 24:th) i used the latest stable version (1.10.10) and it solved the problem. I´m on Mac OS Sierra (10.12.6).
On window 7, i found the issue was because of two reason and both were related to power shell.
First problem was because of execution policy related to power shell script, which can be solved by running the following with administrator privilege.
Set-ExecutionPolicy RemoteSigned
After this, please check the power shell version, in case you are trying to install latest version of mongodb on window 7, power cell version needs to me minimum of 3.0, in my case it was 2.0 and because of that installation was getting stuck. After upgrading power shell to latest, installation went through quickly.
I managed to surprisingly fix this issue by restarting my computer. I was on Ubuntu 18.04, Compass v1.x (somewhere this year).
I understand that the poster is on Windows but this was the first hit on Google.
This seems to be forever error, even in 3.6.3 version, that i've tried today. There are questions about the error everywhere.
The link below
Installation/Update of MongoDB 3.6.2 on Windows Hangs
explains the problem - the install trying to run execute the PowerShell script to download/install MongoDB Compass, which seems to hang due to insufficient rights.
DO NOT install Compass, or install it later with appropriate rights.
The same problem here.
My MongoDB version v4.2.1, compass-1.23 on Win 10 OS.
In MongoDB Compass screen panel, I went to View-> Toggle DevTools.
In Console section there was error indication in red :
"""Error: Command failed: powershell (...'powershell' is not recognized as an internal ..."""
Powershell can be added to environment variables paths:
Please check this:
Powershell' is not recognized as an internal or external command, operable program or batch file
So, I closed MongoDB Compass window. Then I added path to environment variables:
C:\Windows\System32\WindowsPowerShell\v1.0\
And it solved my problem.
You can also add this line too, to enable MongoDB cmd line commands (your location and version can be different):
C:\Program Files\MongoDB\Server\4.2\bin\
Please check this: How to Install MongoDB on Windows 7/8/10 | How to Install Mongo Compass as separate installer

Can't launch MySQL Workbench v6.3.8

I've seen similar posts regarding this issue on the site, but none of the posted resolutions worked for me. When I attempt to launch MySQL Workbench, nothing happens on-screen & 2 application log errors are generated. One is a very generic KERNEL32 event, and the other is .NET related:
Application: MySQLWorkbench.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException Stack: at MySQL.GUI.Workbench.Program.Main(System.String[])
Most of the resolutions I've found online relate to missing prerequisites, which include
.NET Framework 4.5
Visual C++ Redistributable for Visual Studio 2015
I have installed both of these on the machine but am still seeing the same behavior. Can anyone suggest anything else to try?
Upgrading to MySQL Workbench 6.3.9 resolved the issue
i installed MySQL Workbench 8.0.19 and I encountered the same error. When I installed the following package, my problem was solved and MySQL Workbench started.
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
(My operating system is 64 bit and I downloaded-> x64: vc_redist.x64.exe)

unable to close MySql Workbench

Hi I'm using mysql workbench 6.3.8 on Mac OS 10.12
I have a bug. I'm not able to close the workbench properly by using the menu quit or command q.
Could I have miss something during the installation?
Sorry for the late response. Now I use mysql workbench version 6.2.5 revision 0 build 397 (32 bit) and it works fine. (I have worked also around password) – Patrick Lec 5 mins ago

Netbeans refuses to shutdown

An infuriating problem.
My Netbeans IDE 7.2 refuses to shutdown when I try to shutdown my machine.
I have got to use task manager to close the beast.
Its a windows 7 64 bit machine.
I have tried the usual Netbeans forums.
Any Ideas?
PS: I also use the well behaved Eclipse.
from what I'm seeing, you might have a corrupted install of netbeans cause usually it is light on a system. How long ago did you install it? Did you make any major changes before this all started, from evinvorment setting changes to major changes like how the thing complies etc...? I would say, the easiest bet is to back up the settings, if possible, and reinstall or do a repair install, if offered, of netbeans.
Upgraded to 7.3 and I no longer have a problem.
BTW Netbeans 7.3 is great for developing HTML 5 code.