I know I know.... just making a pathetic effort to make the problem look
smaller. If I manage to fool myself into thinking that the rock is not as big
as it really is, then I can be stupid enough to try to push it out of my way.

I'll try with garbageCollect().

There's nothing better than giving birth to a DHTML monster ( aka as "Cool
website that's going to impress our customer no matter what the dhtml guy says
about browsers having terrible performance") that eats as much as 6M on each
reload to make you want this fixed.


Raymond Smith wrote:

> This is still important because onUnLoad doesn't solve for a singular
> dynaminc interface that brings window-widgets in to open portals into new
> subareas without ever leaving the main stage (page).
>
> ----- Original Message -----
> From: "Jordi - IlMaestro - Ministral" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, March 13, 2001 1:53 PM
> Subject: Re: [Dynapi-Dev] The memory leak is about to surrender to my
> fierceful efforts
>
> > Addendum:
> >
> > deleting layers ( tested with delete.html ) causes memory usage to
> increase.
> > Creating some after deleting a lot causes memory to reduce as if the ones
> deleted
> > were effectively deleted when another one is created ( aaaarg !!!!! ).
> >
> > Frankly: If I can get all memory freed onUnLoad I don't give a shit about
> > deleteElement not freeing memory.
> >
> >
> >
> > _______________________________________________
> > 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

Reply via email to