I'm using mySQL's phpMyAdmin (installed via WAMP) with Google Chrome and after using it for a while, I can't load things on phpMyAdmin. It is stuck on the "loading" forever, until I delete all my cookies. Why is this?
Open a web browser, then type http://localhost into the address bar and press ↵ Enter . This should take you to the phpMyAdmin login page.
phpMyAdmin tried to connect to the MySQL server, and the server rejected the connection. You should check the host, username and password in your configuration and make sure that they correspond to the information given by the administrator of the MySQL server.
Once phpMyAdmin is installed point your browser to http://localhost/phpmyadmin to start using it. You should be able to login using any users you've setup in MySQL. If no users have been setup, use admin with no password to login. Then select Apache 2 for the webserver you wish to configure.
To repair a MySQL database, open phpMyAdmin, go to the Databases tab and click on the name of the desired database. Select the tables that need repair by ticking the check-boxes on the left of the table names. Then from the With Selected: drop-down menu choose Repair Table.
I had the same issue and it turned out to be some of my browser extensions. The easiest way to fix this is to basically disable them all (just to be sure) or do it the lazy way: run phpMyAdmin in incognito mode.
Typically when this issue occurs, phpMyAdmin has encountered an error and it sends a request to the server to the error_report.php endpoint, then when the response comes back it will send another request to the server to error_report.php, on and on and on forever. This places increased load on the web server, causing the CPU usage to increase quite a lot. If you're having this problem on localhost, after a short while you may hear your computer fan kick up a notch or two and get louder.
In one case this seemed to happen when some tables were locked and phpMyAdmin was trying to access them at the same time as another process. In another case, session or cookie data seemed to be corrupt/incorrect.
Solutions to attempt include:
Solution 2 worked for me in one scenario and solution 3 was required in a different scenario. In each case high CPU load was observed.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With