Closing an IE popup (twice) while a XmlHttpRequest is running, uses up all available connections.
To reproduce this:
- create a slow XmlHttpRequest (xhr). (Running about a minute or so)
- Open a popup window which executes this xhr. Close it while it's still running
- Open this same popup again. (Second request). Directly close it while the xhr is running.
- Open another popup... et voila... IE Hangs..
This problem is what I was experiencing. After hours of frustrations we found a workaround:
In the onunload of the body tag you must call the "open" method on the same XmlHttpRequest object.
The call of "open" disconnects and stops the old request. Appearently abort doesn't do this
Working code:
WARNING: This solution has only be tested with IE7!
Update 23-01-2008:
Solution for this problem with prototype is. Just put this code in an seperate javascript file. Include this file after prototype.js call iefix_runGarbageControl() in the onunload and the bug is fixed ;-)
// IE TCP/IP Connection Leak FIX, with prototype
if( Prototype.Browser.IE )
{
var iefix_xhrs = new Array();
function iefix_runGarbageControl() {
for(var i=0; i
Update 24-04-2008:
Added: place 'iefix_runGarbageControl()' in the onunload
Note to self: When using prototype don't use the innerHTML property.
Internet Explorer has got a (in my opinion) broken implementation for certain elements.
It is not possible to change the innerHTML content of the TR and SELECT elements.
Fortunally Prototype has fixed these problems in the Element.update method!