So do you think there's a difference between delete c, and c=null as far as
memory-leaking is concerned?
If not, simply changing to c=null might help fix this bug:
Or will changing the order like Stephan suggested harm anything?
see:
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/msg03569.html
This bug has been mentioned before too, but seems only to happen to
some-people sometimes. (especially on Linux I think)
I wouldn't like to go changing anything where memory leaks are concerned
before asking the dragon-slayer :o)
Richard.
----- Original Message -----
From: "Jordi Ministral" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 18 June, 2001 20:02
Subject: Re: [Dynapi-Dev] Attention...
> You wont get any memory leaks in IE unless you reference browser objects.
>
> a = new Array
> fill a with lots of Js data
> unload page
> leak
>
> a = window, document or any HTML element
> unload
> lots of leaking
>
> Of course this depends on browser version and platforms.
>
>
>
> Stephan Tolksdorf wrote:
>
> > >> Could someone please give an example or better explain why IE makes a
> > >> difference in memory handling between delete c and c = null.
> > >
> > > In one word? Microsoft.
> >
> > And in, say, 100 words? To be honest I don't really believe that c =
> > null would cause a memory leak.
> > I'd be very grateful if someone could give a proof for the expected
> > memory leak, for instance an html example. Up to now I have only seen
> > some kind of trial and error methodology and statements weakly backed
> > by arguments.
> >
> > Stephan
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
