Whenever I try to it just crashes, and I haven't been able to find anyone else with this exact problem. I am only trying to delete one cookie at a time. I have run a scan with malwarebytes and removed some viruses but that didn't do anything.
Restarting my computer seems to have fixed the problem for now.
Related
I made a query in phpmyadmin that took a long time and in the end it timed out.
After it timed out, I have been unable to access phpmyadmin again.
I don't get an error, the website just keeps loading and nothing happens.
I've tried accessing the database via scripts, and that works fine, just can't use phpmyadmin.
This has happened a few time before, always after timing out. And I've always just had to wait for quite some time. I usually just try again a few hours later or the next day and then it works. But, that is a bit annoying when I am working on something.
Is there anything I can do to prevent this from happening (other than just making sure my queries won't take so long)? It feels like phpmyadmin is still working on the query, even though it timed out, and that's why it doesn't respond, but I would just like it to stop running the query.
You can reboot the service, I mean, the apache in order to clean buffers etc. Also I recommend you to show the current connections with SHOW PROCESSLIST
Apologies for the lack of details however we are hoping to get some assistance in simply how to get those details.
We are using IDB to store a good amount of data coming off web sockets and put into IDB via web workers. It works fine almost all the time but every once in a while IDB just seems to crash. It no longer shows up in the Application tab of dev tools.
chrome://indexeddb-internals/
Won't even load... DBs fro other sites are affected which makes me think we have stumbled on a difficult to reproduce IDB bug.
The only way to fix the issue is to close down Chrome entirely, sometimes killing processes that won't shut down itself, and start it back up again. Basically the whole engine dies.
Does this sound familiar to anyone and any advice on how to trace it to provide more information?
Cheers and thanks,
Walter.
I'm working on an assignment for school, my files for the website are stored on a distant server which I access via VPN and remote server connection on macOS.
When I modify my html files, the changes aren't reflected immediately, sometimes after a day or two (in fact quite randomly, can be an afternoon, an hour).
It's a bit problematic when you try to have long code sessions. Sometimes, one page actualises but not the others.
I'm not having any problems with my php files, they actualise immediately.
I've tried several things without any changes:
Emptying the cache
Trying on different web browsers
Disconnecting from the server and VPN
Waiting :)
System infos :
macOS 10.12.2
Safari 10.0.2
Thanks for the help, I personally think it's a problem with the server, but I won't be able to change that, hopefully, it's something I can fix.
I'm a web developer, and often run scripts to fix things that might time out due to server or browser settings. In the past, Chrome would just spin and spin as long as it takes until the script was done - even if it takes an hour, but they changed things and now, it imposes its own cutoff time is the server doesn't respond fast enough while the server continues to execute the script.
Now, this is annoying, it forces me to log events to a file, rather than just dump to the screen, but the worst part is Chrome thinks it is a great idea to try reconnecting to the URL after it times out. That then starts to execute the same script which probably is already running again.
The issue here is that I often create scripts to run ONCE and never again, and if the script is run more than once, it could completely destroy things.
Say I create a script to remove the first 4 characters from each field in a 1 million row database. Running the script via Chrome would eventually time out and then it would run the script again several times without letting you know. Suddenly, the data that was already reduced is being reduced again, destroying the data.
This is a serious concern that was never an issue before because Chrome wouldn't automatically try to reload a page that failed to load. So, I'm looking for a way to disable this new feature and stop Chrome from automatically reloading on a failed page load. It displays an error page saying "Click here to reload", but it completely ignores the user and decides to reload whether you click it or not.
I just ran a script to copy files from an EC2 instance to an S3 bucket as part of some cleanup, but I see from the logs that it actually ran 4 times before I closed the tab - even though I never asked it to reload. That meant it copied these same files 4 times. Fortunately, in this case, it just wasted S3 access, since it overwrote the existing files.
Yes, I realize that there are many ways of preventing the script from running more than once, from flock to renaming the file immediately after executing it. The issue is speed. These fix scripts are not intended to be full blown applications complete with all the bells and whistles, they are meant to be a fast way to apply a fix. I would rather make a change in Chrome to disable the new way it works so that I can continue to work as I have for over 10 years.
This is referring to an auto reload, and I'm not calling it a "refresh" because the page never loaded in the first place. This has nothing to do with the millions of questions regarding refreshes, and that is all I get when trying to search this problem out.
Probably this can resolve the issue:
go to chrome://flags/
set to Disabled flag Enable Offline Auto-Reload Mode (or Offline Auto-Reload Mode)
set to Disabled flag Only Auto-Reload Visible Tabs
Relaunch browser
Now I have page with error ERR_CONNECTION_RESET that does not reload itself automatically anymore
I just installed a fresh copy of mediawiki on http://konton.us/wiki
I was all happy playing around with my wiki, filling up the place with information and suddently, when I created an article by the name of Gameplay_Mechanics, it all went dead.
http://konton.us/wiki/Gameplay_Mechanics
I got this error:
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "". Database returned error "1205: Lock wait timeout exceeded; try restarting transaction (internal-db.s76387.gridserver.com)".
I was able to fix it by 'emptying' the article and then saving it - only to repopulate it again but...it happened less than 1 day later...again, so I'm kind of wondering what is the ACTUAL ROOT CAUSE of this ridiculous error.
All help is appreciated
Try deleting the page, then recreating it with a slightly different name. It might just be a weird fluke thing having to do with that page specifically.
Are you using MySQL 5.1.26rc for a specific reason? Maybe upgrade to 5.1.49?
http://konton.us/wiki/Special:Version
This looks more like your database server being too busy. This error is often a sign of deadlocked transactions, although I'm not sure MediaWiki even uses transactions.
Are there many users visiting your site? Perhaps you're sharing your hosting with another high-traffic site?