We have a Wordpress based website (rendeljkinait.hu), and we face freezing issues while editing articles when using Chrome. When I hit the save button for the 7th time without page reload, the article editor freezes during save and I get "waiting for available socket" error in Chrome. No matter how long I wait, the editor won't save until I reload the page. When I'm using Firefox, everything is fine, no matter how much I hit the save button. Current Wordpress version is 5.2.3, but error occured in former versions too.
I investigated the error, and found it is caused because Chrome never closes the open sockets until I reload the page. So until hitting the button 6 times everything is fine, since Chrome and other modern browsers allow to have maximum 6 paralell connection to a single host. But after I press the button for the 7th time, there is no space for another connection, so Chrome is waiting for the older connections to get closed, but it never happens.
Here's a screenshot from net log
Using Firefox I observed that it always closes the connection after the save is successful, so only 1 connection is active all the time, it never exceeds the 6 paralell connection limit. I attached Chrome netlog file here, you can view it here. I also attached a video showing Firefox closing the connection here (107.6.*.** is our servers IP).
For various reasons we have to use Chrome, so I would like to find a solution for this problem, but I'm completely stuck. Does anyone have a suggestion what could cause the problem and how to solve it?
Thanks in advance!
I have the same problems with chrome and gutenberg.
It is impossible to do any heavy editing on the site, so I use firefox for all admin related stuff.
Haven't found a solution either...
For anyone who might find this topic with similar problem: seems like it was a Wordpress bug, a Wordpress update solved the issue.
Related
I've got a local webserver (apache) running on my laptop and it is serving up a content management system successfully. Everything looks okay in both IE9 and Firefox.
Today I tried to demo it to someone and the elements were completely misaligned, looked terible in IE9. Still looked okay in Firefox. Tried to figure out what was wrong, even restored an earlier known good build and still messed up. There was no wireless connection at that site and no wired connection either.
I'm back at my place now to diagnose the issue, and there is no issue! By process of elimination, I deduced the ONLY difference between then and now is that now I am on the internet. Bear in mind, I am NOT retrieving anything from the internet for this site. (Not that I am aware.)
I switched off my wireless connection and immediatly my pages started rendering in screwed up fashion again. These pages have tons of framework generated divs and CSS classes so it is not clear where the breakdown occurs... but here is my fundamental question:
What could IE9 be doing that simply shutting off my internet connection would cause it to stop rendering a locally served page properly?
Use a network analysis tool like Wireshark to capture the packets that Internet Explorer send (or tries to send) out. You probably will find something there.
There are two things I can think of:
You are retrieving some parts from the internet, even though you are not aware of it. Maybe some JavaScript code loads something, or you have url() values in your CSS.
It might have something to do with the compatibility view of the IE.
You could try to use a network sniffer to find out, what the request is.
instead of going all the way to WireShark why don't you try the built-in developer tools?
Press F12, select the Network tab and start capturing traffic right from IE9. It will show you everything it requests for.
i've recognized that on google chrome browser every second postback of my asp.net application is a bit slow (~1 seconds)... every other shows up immediately. internet explorer is doing fine on every postback!
someone any idea?
regards
Do you mean that when you are debuging your asp.net app using google chrome that it is running slow?
I had this problem also at one point and was to do with your host file. See this post here for a solution to his problem
https://superuser.com/questions/43823/google-chrome-is-slow-to-localhost
I've noticed that chrome frequently has connection issues, not just during debugging. I've seen this on multiple machines, different OS's. Sometimes if we just leave chrome idle for about a minute or two it will completely not respond when trying to do a post back.
After seeing the quality of a number of google's other products this appears par for the course.
Bring up the console to see if there's any weird stuff going on there. Also, view the Network tab.
We have an asp.net site running, which has been working fine for some time, but recently I have been experiencing some issues with IE8.
On posting some pages - mainly on our development server, although on staging too - we get an occasional "Internet Explore cannot display the webpage" error along with the button asking to diagnose connection problems. IE only seems to wait 10 seconds before timing out. I know that the page itself may take longer to load the first time (on dev and staging). So press F5 and everything then works fine.
Is there anything that should be done in the aspx page to tell IE to wait a bit longer?
I thought I had read that the default timeout supposed to be 90 seconds or something for browsers.
A bit more info:
It mostly happens on a POSTing a signup page, but that is just because I test that page and it starts the IIS App, makes the first connection to SQL and pre-caches some information. That first time the page can take 10-15 seconds to come back. IE8 times out after 10 seconds as it has had nothing back.
This happens on a dev W7x64 machine with 8GB RAM, as well as on a staging server WIN2008.
Having googled around a bit, some people are seeing the same problem, but no conclusive pointers to the problem or a solution.
It isn't a connection problem; everything works fine in Firefox, Chrome and even IE7; I have tried with add-ons disabled and resetting IE settings, still happens.
Ideas welcome.
Try this out
<httpRuntime executionTimeout="15"/> under system.web in the web.config
A 10 second timeout might be a usability tool in disguise. 10 seconds is a pretty long time. Js capable browsers are > 99% now, why not push it off over Ajax and poll until the long work is done, then redirect to the next page? You could show the user more useful progress info in the meantime. If for some reason the next page itself is the source of the slow down and cannot be separated from its slow parts, you could finish by precaching the next page then redirecting.
Check your Application pool Advanced settings in IIS. It may be lower than is normal. Maybe the Ping period? Mine is 30secs
I think that the long term solution is not actually related to timeout configuration.
You're saying that only the first request takes a long time, and it takes > 10 seconds, so you should issue a warm-up request first after installing your application in a way that the first request load is never experienced by the end user.
I'm trying to fix a browser history issue. A customer of ours has a ASP.Net intranet page running for a while now. A colleague made it. Recently they asked to fix the "Back button" we made on their page (the application).
It looks at the sitemap and when clicked loads the parent page. However, in some situations I have to use "javascript:history.go(-1)". All worked fine on our test systems but when we deployed it on their test server it started to malfunctioned. We noticed that their production environment has the same problem.
Apparently all their machines (running IE) can only go back one page in the browser history. This is not intentional. We had one of their IT staff trying some other browsers and OS's. Apparently the problem (so far) only occurs when using IE. All other browsers they tested were fine. On my development system this problem doesn't occur. Also when I let someone else look at the site the problem doesn't occur either.
I have checked what their browser history length is set to and its 20 days. I tried searching here on stackoverflow but the only relevant answers concerning browser history didn't help.
How to clear browsers (IE, Firefox, Opera, Chrome) history using JavaScript or Java except from browser itself?
Also pushing the back button (the one in IE), it only works for just one page back. There is no way we can navigate more than one page back.
How can I fix this?
Server: W2k3 R2 SP2
Clients: XP I guess / IE 8 mostly
This looks very much like a local configuration problem within your customer site and therefore unlikely to be seen elsewhere, as you've proved yourself. What you need to discover is how this could be restricted and SO isn't the place for that. You might want to try posting on SuperUser for further assistance.
I have a very unusual problem that actually took me quite some time to even locate the root cause. I have an ASP.Net 3.5 web application running on Windows Server 2003. I was getting reports from users that said every so often the application would refresh on its own, without user interaction. This was unusual as I have not coded any client side refreshes. After much troubleshooting I narrowed this down to an issue with Internet Explorer (both 7 & 8). FF, Chrome, and Opera do not exhibit this behavior.
Basically, this only happens the first time a user visits the site on a new instance of IE (either a new window or new tab). If the user goes to any page within the site, and then does not interact with the site again, after 6 minutes the browser refreshes! After that refresh, as long as it is the same instance of IE, no matter what page on the site you visit, and no matter how long you let it sit, you never see the refresh again. This has really baffled me, and has become a major problem as this app has data entry forms that take longer than 6 minutes to complete. Unfortunately, if the user gets caught by this refresh bug, anything they entered is lost because of the post.
I need help!! Any advice or options to try would be greatly appreciated. Thanks!
(no, I cannot require them to use a better browser as this is a corporate environment with restrictions set to use IE for non-technical users)
It's a stretch, but maybe you have a 3rd party component that's adding a meta refresh tag only for IE (see http://www.w3schools.com/tags/att_meta_http_equiv.asp (refresh value)). Or maybe there is client-side code generated somewhere only in the case of IE that puts a location.reload() or location.href = someLocation a client-side script block in your markup.
Have you compared the HTML markup in IE and and FireFox? Are they the same? That's where I would start. If they end up being the same, look at script references and search for location.reload() or location.href.
And actually maybe before that, run IE without Add Ons enabled and see if it refreshes. To run without addons, do this at the command line, "C:\Program Files\Internet Explorer\iexplore.exe" -extoff