-Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Lasse
> Lindgard
> Sent: Thursday, April 19, 2001 4:37 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [Dynapi-Dev] Garbage collection
>
>
> Ohh no. NS is doing just fine. And NS6 is doing
I tried to put it into the DynAPIObject unloadhandler at various positions.
It didn't seem to make any difference at my IE55 or IE6ß
/Lasse
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, April 18, 2001 10:09 AM
To: [EM
it should claim more than beta status.
/Lasse
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Scott Andrew
LePera
Sent: Wednesday, April 18, 2001 7:50 PM
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Dev] Garbage collection
I thought the majority of m
I thought the majority of memory leak problems happened in Netscape
instead of IE. Am I mistaken?
Regardless, part of the NS leak problem is probably due to (but not
limited to) two factors:
1. NS doesn't do garbage collection until a new page is loaded (or
reloaded)
2. multiple document.write(
; finishes the reference clipping on behalf of deceased "object
a".
- Original Message -
From: "Robert Rainwater" <[EMAIL PROTECTED]>
To: "Raymond Smith" <[EMAIL PROTECTED]>
Sent: Sunday, March 11, 2001 9:07 PM
Subject: Re: [Dynapi-Dev] Garbage Collection
>
This is where Mozilla messes everything up. Try doing any type of
recursiving deleting in Mozilla and it will hack up since it follows
all pointers to objects and since we use recursive pointers like:
dlyr.doc.lyrobj = dlyr it goes crazy. I would love to see a solution
for Mozilla.
--
Robert
JS files.
_
- Original Message -
From: "Raymond Smith" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 09, 2001 4:57 PM
Subject: Re: [Dynapi-Dev] Garbage Collection
> This is a JS object by Bob Clary that serves as a base object in a JS
> hiarchy, it has an expl
This is a JS object by Bob Clary that serves as a base object in a JS
hiarchy, it has an explicit call to destroy() built in with a brief
discussion as to why it's needed.
http://www.mindspring.com/~bobclary/base/docs/xbObject.html
Class xbObject NameClass xbObject - root of Javascript Class Hie
That's funny, one hour ago I read this exact same document.
I tried to apply this code in several different ways, setting everything to
null, and calling CollectGarbage(), you see it changes the ram usage
slightly, but not much difference.
I also noticed that changing to another URL doesn't seem t
