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
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:
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
3 matches
Mail list logo
