it seams to me that there are memory leaks eaven in
eventsHandlers(listeners);
Is there any chanse that the Event (or mouseEvent ) objects ar not
RELEASED ???
Bogdan Pietroiu
IT Specialist
MIS Department
Flamingo Computers SA
tel: +40-1-236.2002
fax: +40-1-236.2004
e-mail: [EMAIL PROTECTED]
we
what's wrong with DynAPI.document.all.length() ?
- Original Message -
From: "Eytan Heidingsfeld" <[EMAIL PROTECTED]>
To: "Dynapi-Dev" <[EMAIL PROTECTED]>
Sent: Wednesday, February 28, 2001 10:54 AM
Subject: [Dynapi-Dev] Memory leaks
> As you sa
As you saw I posted the thing that fixes leaks in IE5 (elements) and should
fix in NN6 (not tested yet).
Another thing we need though is some kind of external counter of every
widget something like adding a variable called DynLayerCnt(an array) and
then adding every element to it and each layer g
D]]On Behalf Of Doug Melvin
Sent: Monday, February 05, 2001 3:47 PM
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Dev] Memory Leaks???
Yes.
And in IE5.0 (tho not as bad)
And it's not just DynAPI 2 either.
IE 5+ has a know problem with freeing up nested objects (objects within
other objects)
such
;[EMAIL PROTECTED]>
Sent: Monday, February 05, 2001 12:15 PM
Subject: [Dynapi-Dev] Memory Leaks???
> Has anyone had any problems with memory leaks and the new DynAPI when
using
> IE 5.X?
>
> Mike Ellis
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL
Has anyone had any problems with memory leaks and the new DynAPI when using
IE 5.X?
Mike Ellis
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 03, 2001 20:27
To: [EMAIL PROTECTED]
Subject: Dynapi-Dev digest, Vol 1 #189 - 6 msgs
Send Dynap
