Some are default. A corrupt add-in may also cause an Internet Explorer freeze. To check this, right click on the icon of Internet Explorer, and select the option Run without Add-ons. If Internet Explorer begins working properly, one or more of the add-ons are corrupt, and you should follow the method mentioned in the next paragraph to fix the issue.
If it is not working properly even with add-ons disabled, you may proceed to step 3. To locate the plug-in creating problem, start Internet Explorer normally again and disable all plug-ins see the NOTE and Image in the first section. Enable each plug-in—one by one—after browsing for some time with each plug-in. You can isolate the plug-in causing the problem as Internet Explorer 8 hangs as soon as you enable the corrupt plug-in. Click on the Disable or Remove button after selecting the plug-in in the Manage Add-ons window to fix the problem.
There is high possibility that one of the processes on your machine is conflicting with the functioning of Internet Explorer.
To check this, you will have to test your Internet Explorer in a clean boot environment. The link also explains how to isolate the process interfering that causes Internet Explorer 8 to freeze. If your problem is not fixed, you will have to go for a reset as mentioned in the next step. Resetting Internet Explorer restores the browser to the state when it was first installed. If the browser works fine after resetting Internet Explorer, your problem is fixed.
Otherwise you will have to re-register all components of Internet Explorer 8. If the problem disappears after re-registering all components, you are done with troubleshooting Internet Explorer 8.
If the Internet Explorer 8 freeze appears again, the final resort is to reinstall Internet Explorer 8. If you set this policy to 'Disabled', enhanced hang detection is disabled, and users will get the basic Internet Explorer hang detection behavior.
Toggle navigation Group Policy Home. Configure enhanced hang detection for Internet Explorer mode Enhanced hang detection is a more granular approach to detecting hung webpages in Internet Explorer mode than what standalone Internet Explorer uses. However a few days ago it suddenly stopped working in IE10,9 and 8. On certain pages when clicking a button the page hangs for up to an hour. Some of the PCs have not been rebooted for months so we do not think it is due to an update to IE.
Also if we deploy the application to a different server everything works fine for IE too It also does not happen when running the site from a development environment. So we have discovered that it only happens when the site is running on either the live server or the test server both almost identical but not quite and even then it only happens when accessing the site from IE!
The live and test servers are both win while the server that it does work on is win and my dev environment is on windows 7. We have discovered the root of the problem, although not why it is suddenly causing an issue. We have some buttons where a ClientSideOnClick event is added manually. This seems to cause two postback methods to be added to the button one manual and one automatic. If we do not add the manual event then everything works fine.
Can we disable the autoeventwireup just for the buttons? Then we discovered as posted above that there were some instances where a buttons were given two JavaScript postback events. These buttons have not been altered for at least 3 years and have been working fine even if it is not best practice or even wanted behavior , however installing 4.
Now this means we can finally get the pages working again. However we still really do not know why installing. Even more baffling is why it only broke in Internet Explorer. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
0コメント