Well, it is still leaking. Overnight iexplore.exe had grown from 30M to 300M, so I guess that wasn't the problem. Anyone else have a slightest clue?
And what's weird is that it's only IE that's leaking memory. It's really tempting to just ditch IE, but unfortunately it still has a big market share... On Mar 9, 1:18 am, mif86 <finsta...@gmail.com> wrote: > Ah, maybe a race condition occours or something, then. > But it's strange that I can only see it happening in IE. > > I've modified the code to run another load() in the callback from the > first load(), instead of periodically. > It seems though, that it still keeps growing. > I'll leave it on over night and check if it has grown out of my system > memory by tomorrow! > > (http://mif86.com/memtest3.htm) > > Thanks mate :) > > On Mar 9, 12:58 am, "comslash.com" <comsl...@gmail.com> wrote: > > > I would have to guess that because you are using the .load() in such a > > rapid way that the load commands are stacking up, you will want to > > either increase your interval time or set something up that only one > > load command is going out at a time. > > > On Mar 8, 7:42 pm, mif86 <finsta...@gmail.com> wrote: > > > > Hi! > > > > I'm having problems with all ajax updates, $("#element").load() etc., > > > gradually eating up IE 7's memory. > > > > Simple test case to reproduce:http://mif86.com/memtest.htm > > > > It periodically loads another page's html content (http://mif86.com/ > > > memtest2.htm) into a Div using jQuery's $("#element").load > > > ("memtest2.htm"). > > > If you watch the memory usage in internet explorer, it will grow > > > linearly with time. > > > > I've been googling all around, trying lots of tweaks and fixes, but > > > nothing seems to work. Is there something i'm misunderstanding, or is > > > there a bug in jQuery? or something else? :S > > > > Thanks
