I think I'm seeing a situation where sendXMLHttpRequest is leaking
references when used in IE, and I suspect the cause is
sendXMLHttpRequest's use of closures. At the very least, the
sendContent local variable ends up living longer than it should, but
due to IE's brain-dead cyclic-GC, I think req forms a cycle which
prevents the closure being discarded.

If I rearrange things so sendContent isn't captured by the closure, the
worst effects go away, but I expect the closure and request still
linger around, but I lack the tools to confirm this.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"MochiKit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~----------~----~----~----~------~----~------~--~---

Reply via email to