I recently installed PostgreSQL 13 on windows 10 and the PostGIS extension via the stack builder. However, when trying to launch the shp2pgsql-gui application to import a shapefile, I get a "libsqlite3-0.dll was not found" error. I can see the file under the bin folder, so I'm not sure where the problem is and googling did not help very much. I wonder what the problem may be because the installation seemed pretty straightforward to have done something wrong.
Copying the "libsqlite3-0.dll" file from \PostgreSQL\13\bin to PostgreSQL\13\bin\postgisgui and then running the shp2pgsql-gui application seemed to fix this issue for me.
This problem can occur for different reasons, but I recommend that you download that .dll from the following link (https://es.dll-files.com/libsqlite3-0.dll.html). Then replace the file in the installation folder.
Since upgrading from MAMP 3 to MAMP 4, the GUI hangs on each action. Clicking something like the menu occurs after around 30 seconds of the spinning wheel of death. This happens for any action within the interface. Running 10.12.2
This almost makes the software unusable, as I can't configure the interface to begin development.
My experience was identical. Searching for some errors I ended up running Tools > Verify MySQL Databases... Among tons of OK'ed databases, several had errors - innodb_index_stats, innodb_table_stats, slave_master_info, slave_relay_log_info, and slave_worker_info.
From here a search lead me to mysql error: Table “mysql”.“innodb_table_stats” not found.
So, I deleted all the .frm and .ibd of the tables above and I ran the five-tables.sql file in Terminal: source five-tables.sql
Now MAMP Pro 4 runs smoothly and responsive.
Thanks, Kay Nelson.
I ended up doing a search for MAMP in all parts of the file, and removed every reference to it, after running the uninstaller.
I also removed references to any PHP & memcache not in the /Applications/MAMP folder.
I renamed /Applications/MAMP to /Applications/MAMP-old and reinstalled. This set everything up fresh and appears to be working. Something with a conflict with a system binary or other package was causing the issue.
I am using MySQL Workbench 6.3.7 build 1199 CE (64 bits) on a Mac with OS X Yosemite 10.10.5. I am connecting to an Amazon RDS MySQL instance.
When I enter a simple query such as
select * from `devices`;
and click the lightning-bolt-with-cursor icon, the query starts, indicated by the spinner activating next to the "SQL File 4" tab in the following screenshot. However, the query doesn't complete and it just hangs. The white-hand-in-red-stop-sign icon is disabled.
I can only force quit MySQL Workbench from this point on. If I try to do a regular quit, nothing happens.
How can I consistently run a simple query on my database? Sometimes it works (maybe 10% of the time), but it mostly just hangs.
UPDATE 3: The problem is fixed for MacOS HighSierra in MySQL Workbench 6.3.10.
UPDATE 2: It looks like the bug is recurring again in MacOS HighSierra. See https://bugs.mysql.com/bug.php?id=83658 for more details.
There is an unofficial build that fixes the problem. You can download it at: https://drive.google.com/drive/folders/0B2fTesDcrHzVRGVFWEdILWpuaEE?usp=sharing
The build was created by Bob Davenport. See https://bugs.mysql.com/bug.php?id=87714 for more details.
UPDATE: The bug is fixed in MySQL Workbench 6.3.9.
----------------------- original answer -----------------------
It is a known MySQL bug: http://bugs.mysql.com/bug.php?id=83658 caused by GateKeeper Path Randomisation introduced in MacOS Sierra. See https://weblog.rogueamoeba.com/2016/06/29/sierra-and-gatekeeper-path-randomization/.
A possible workaround is to remove the Quarantine ACL:
xattr -dr com.apple.quarantine "/Applications/MySQLWorkbench.app"
I found that if you use the latest 6.3 version, that in order to get queries to work, you have open a first connection and ignore it and then open a second connection. This creates two tabs in the workbench. If you perform your queries in the second tab, it works. If you try in the first tab, it hangs.
I also have found that you have to do a force quit the workbench.
I hope the mysql folks get this fixed.
To resolve this issue, I downgraded MySQL Workbench to 6.1. Now I am able to run my query and it doesn't hang.
In my case, it was changing the connection->ssl->Use SSL setting from "If available" to "No". Workbench 6.3.8 on OSX 10.12.1 now works for me.
The spinning wheel of death is due to the new feature introduced in the Sierra update called "Gatekeeper Path Randomization".
Follow the instructions:
Open MySQL Workbench :)
Right click on your connection (most likely “localhost” or “127.0.0.1”)
Choose “Edit connection”
On the right hand window select “Connection > SSL”
Change “Use SSL” from “If available” to “No”
Now click on the tab “System Profile”
Choose “MacOS X” as System Type
Click “Test connection”
Credits: http://cordobo.com/2398-mysql-workbench-6-3-macos-sierra-hangs-on-simple-queries/
The version 6.3.9 solved the problem, but this version is not showing in "Check for upgrades" option, you need to download directly from the site.
MySQL Workbench official download page
6.3.9 fixed the issue in the mac. Here is the link MySql 6.3.9
At last I have downloaded MySQL Workbench 6.3.10 and install MySQL Workbench 6.3.10 and solved my problem. I have downloaded MySQL Workbench 6.3.10 from bellow link https://dev.mysql.com/downloads/workbench/
It is working for me.. I think this will work for you..
I found that deleting the cache and workspaces folder contents (~/Library/Application Support/MySQL/Workbench) it works again. What I haven't found is how to ensure it doesn't hang again :-(
I also found that if I manually close the Connection tab from the menu and exit WB from the menu and not from the OS window buttons it seems more stable next time.
PS: I am using SSH connection so it may be due to this but it is not always happening.
UPDATE: A clean install and no SSH configurations the issue still persists. Unless you manually go and delete the cache folder files it continues to hang.
I was getting around the problem for awhile by deleting the user library folder and dropping back to version 6.2.5 ... but today found the problem was back. So today I deleted the user library folder and dropped back to version 6.1.7. It's working again, for now.
In my case, the IP address changed where mySQL was served.
Flushing the DNS fixed it for me:
sudo dscacheutil -flushcache;
sudo killall -HUP mDNSResponder;
say cache flushed
This seemed to help some of the time, but not 100%:
Connect to the database with a different user, and then re-connect with the original user.
I'm about to downgrade like the accepted answer says though, as this doesn't solve it every time.
This is still an open bug in 6.3.8:
https://bugs.mysql.com/bug.php?id=82231
The possible workaround is to open secondary tab with the same connection and work in there. However it crashes anyway from time to time.
Until the bug is fixed I use free Mysql Workbench aleternative for common work. For mac users I would suggest https://sequelpro.com.
Upgrade to 6.3.9 fixed the issue. The 6.3.4 was hanging on queries for me. Unfortunately the Help > Check for Updates didn't indicate any updates were available, so I went to the source.
This can probably help as a temporary/immediate solution. If I try to manually type the below query, MySQL Workbench hangs, especially at x.*
SELECT
x.*
FROM x_table x;
But if I write the SQL in another editor and paste it in MySQL Workbench and run the query, it doesn't hang.
Versions: MacOS Big Sur (11.2), MySQL Workbench 8.0
My Netbeans has been insanely fast for over 2 years, until this morning. Something strange, however, is now happening. Every time i press "copy and paste" ... so CTRL-C, it goes slow. This is what I see:
So, the moment I press CTRL-C, that shows in the bottom, my entire machines goes into super slow mode, and then 5 seconds later it stops.
I've considered maybe there's a keylogger on my machine, but can't find anything. And it's only slow when I copy and paste from Netbeans, nothing else. Maybe Netbeans is sending data out some other way?
Any ideas why Netbeans would just go slow like this?
UPDATE
I only have one project open
I've disabled the git and subversion plugins
I am working on a Laravel project
It's slow when I copy from a VIEW or when I copy from a CONTROLLER (I know css files often go a bit slow because of Parsing, so I figured mentioning this is probably worthwhile)
I followed the advice at the end of this article: here and uninstalled "BlueStacks". Problem solved.
UPDATE
Just in case the article gets deleted, here is the advice the user gives on that page:
I meet the same problem. When I copy a word in the IDE, the IDE does not response until 2 or 3 seconds. I did not confront this problem until few days ago. I try to use the latest netbeans and the latest jdk, but that does not work. Then I find someone said http://bugs.java.com/bugdatabase/view_bug.do?bug_id=5078787 is the problem. And the problem is somewhat about the COM in windows. So I try to install the netbeans to another Win7 PC, and the problem is gone. In that case, I guess the problem is not the netbeans, but some other application in windows. Later I uninstall some of the application I just installed few days ago. And the IDE works right now. The applications I uninstalled is "imc studio" "imc license manager" and "blueStacks" an android simulator. I guess these application may have influence to the COM of Win7. Hope my solution will help to this bug.
You can also just stop the BlueStacks Agent process from Task Manager while you're using NetBeans.
I am experiencing a problem where Rational Application Developer 8 consistently hangs indefinitely on startup. I've only been able to find a partial solution: I can get RAD to start up if I delete the <n>.tree file in the workspace's .metadata.plugins\org.eclipse.core.resources.root directory. Once started however, all projects must be re-imported.
What I can't seem to solve is the underlying issue -- the issue recurs after every shutdown of RAD, and I'm having to delete the .tree file and re-import the projects each time I start the app. Shutting down RAD normally does not prevent the problem from recurring; neither does removing all projects and cycling RAD with no projects (problems start again immediately the first time RAD is shut down with projects still imported). I've even created a new workspace from scratch, but it didn't help either.
I'm at a loss. If anyone has experienced this, any insight would be greatly appreciated.
I am currently experiencing the same problem with an older version of RAD and haven't found a working solution yet so far, but you might get some pointers from here:
How do I prevent Eclipse from hanging on startup?
At any rate, you can check the ./metadata/.log file in your workspace for useful information about where exactly it hangs.
There are many background process starts when Eclipse or RAD starts. You can disable the background process which is not required. These can be found under Window->Preferences->General->Startup and Shutdown.
Delete Temp files under /tmp folder and restart RAD...
Worked for me...