Interesting, I've, also, seen the = null; proposal before, but not the
= function(){}; one. Doing some poking around I found mention of it
here:
http://www.ilinsky.com/articles/XMLHttpRequest/#bugs-ie-leakI just experimented around with the change and posted it into a separate branch: http://github.com/jquery/jquery/commit/fe6c86d53046b0f4d648f61c0b8e75387af65152 Concerning memory usage I'm getting (in IE Drip, using IE 6) when running the jQuery Ajax test suite: Without patch: 19783680 bytes. With patch: 20013056 bytes. Without patch (again): 19820544 bytes. so about 1/5 - 1/4 MB increase in memory usage binding to xhr.onreadystatechange - doesn't really look like it's working as one might expect? --John On Wed, Dec 30, 2009 at 10:22 PM, jblebrun <[email protected]> wrote: > On Dec 30, 7:00 am, Julian Aubourg <[email protected]> wrote: >> If only it could be enough to set onreadystatechange to null :( > > I wasn't proposing to set onreadystatechange to null, I was proposing > to change it to |nop|, a no-op function (that is, a function that has > an empty body). Sorry, I should have been a little more explicit about > that. As Matt Kruse has just pointed out, this solution has been long > known. > > Cheers, > > jbl > > > -- > > You received this message because you are subscribed to the Google Groups > "jQuery Development" 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/jquery-dev?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "jQuery Development" 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/jquery-dev?hl=en.
