One way around this in your app and apps like yours is to invoke the
IE garbage collector by calling the GarbageCollect function. You would
want to do this every so often are important clicks/exchanging.
Calling this method should release any memory that IE would normally
release on refresh.
Jus
Some progress...
by using a garbage collection bin (a dummy div to appendChild and then empty
the innerHTML), the DOM usage is stable now. Code:
jQuery.fn.discard = function(){
var garbageBin = document.getElementById('IELeakGarbageBin');
if (!garbageBin) {
garbageBin = document.cre
I have some problem in creating the ticket. It always timeout when I
submitting... I will try later.
Anyway, here is an example about it.
Load it in IESieve , cilck refresh rows or set interval and watch the memory
and dom usage.
Test Mem Leak in IE6
var da
If you could create a ticket and a test case for this it would help a
lot! I believe I could find some time to investigate it in detail
soon.
--
Brandon Aaron
On 5/21/07, Jacky <[EMAIL PROTECTED]> wrote:
Hi all,
I'm dealing with the IE memory problem.
There is an IE leak called 'pseudo leak',
4 matches
Mail list logo
