There's a memory test I used before to test Eytans tcanvas:
http://www.dynapi.f2s.com/dynapi/tcanvas/stress.dynlayer.create%20wtime200.h
tm
It creates 200 dynlayers, and times this.
When we had the memory leak (up till v 2.51) this time would keep increasing
after refreshing IE5, and running it again.
Ram was not being released after a refresh.
I used Taskinfo2000 to measure mem usage.
I don't think changing it to c=null will influence anything in a bad way.
Unless someone knows different I think we can change this, and close this
bug.
Richard.
----- Original Message -----
From: Stephan Tolksdorf
To: Doug Melvin
Sent: 19 June, 2001 15:39
Subject: Re[13]: [Dynapi-Dev] Attention...
> Then test it.
> I'm sure we don't need to hold your hand.
I asked on this list to learn the facts the core developers are
basing their opinions on. Sure I can do everything on my own, but - as
I see it - we all do profit if we exchange our experiences and try to
improve our understanding of the issue together.
Your answer wasn't productive at all.
Ok, I now tested the different methods for two hours, at least I tried
to do so (JavaScript and Browsers are a cruel programming
environment esp. for memory debugging!).
I couldn't notice any difference in memory handling for the three
different routines (IE5.5 on Win2k, IE4 on Win98 and Mozilla on
Win2k): c = null, delete c and doing nothing.
I based my conclusion on the memory the browser process allocated while
playing with the attached html page.
Does someone know a better testing method?
Stephan
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
