Damn! I thought you had a real cure for the leak.
Most applications create much less that 1000 layers. Even 100 seems like a
high number for a business application (like a pulldownmenu and a scrollbar
plus a couple of buttons).
I doubt that it is the minimum that IE wastes. There are lots of pages out
there that uses dhtml. I can't seem to find any other pages than dynapi that
leaks more than a few kilos.
I think however that a good clue to freeing memory is that DynAPI contains
html-elements within js-objects.
Perhaps there are more places where something similar happens ?
Well, I have production code to ship. So I guess that I'll have to rewrite
my dynapi code to non-dynapi code.
Back to basics :(
/Lasse
Well, keep up the good work guys. I am sure that DynAPI will be a great tool
for web-developers once the leak is plugged.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Eytan
Heidingsfeld
Sent: Monday, March 05, 2001 2:30 PM
To: Dynapi-Dev
Subject: [Dynapi-Dev] AntiLeak
Ok,
Here is the dynlayer with my freeing memory. It doesn't work 100% on 100
dynlayers from 8.1 MB to 9.5 MB on creation and then to 9.3 MB on free. But
that I think is just the minimum that IE wastes. Because with 1000 dynlayers
from 8.5 MB to 16 MB down to 9.9 MB
Which is a big difference. I'm going to look into improving this but
currently am a it busy.
8an
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
