Hi,
In event.js, the current version of the deleteChild() function is:
p.deleteChild = function(c) {
c.removeFromParent();
c._delete();
};
As far as I can tell, _delete() is a null function (set to
dynapi.functions.Null inside event.js and not defined anywhere else). It
certainly leaks me
x27; event fires.
> > > Could it be that the _destroy function is unable
> to
> > > finish before the page
> > > is unloaded, thereby causing some object
> references
> > > to be lost? This would
> > > explain the memory leak.
> > >
>
D]>
Cc: "Jeremy Wanamaker" <[EMAIL PROTECTED]>
Sent: Monday, July 28, 2003 11:53 AM
Subject: Re: [Dynapi-Dev] memory leak
> Hi Jeremy,
>
> This should fix the error. Make the change to the
> dynlayer_base.js file.
>
> p._destroyAllChildren = function() {
- Original Message -
From: "Raymond Irving" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Jeremy Wanamaker" <[EMAIL PROTECTED]>
Sent: Monday, July 28, 2003 11:53 AM
Subject: Re: [Dynapi-Dev] memory leak
> Hi Jeremy,
>
> This should fix th
he page
> is unloaded, thereby causing some object references
> to be lost? This would
> explain the memory leak.
>
> Jeremy Wanamaker
>
> - Original Message -
> From: "Raymond Irving" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
>
Could you please supply an example showing this error?
I think this has something to do with the ._destroy()
function
--
Raymond Irving
--- Jeremy Wanamaker <[EMAIL PROTECTED]> wrote:
> I been working with DynAPI 3 for a couple of weeks
> now. Overall, I'm very
> impressed and optimistic about
I been working with DynAPI 3 for a couple of weeks now. Overall, I'm very
impressed and optimistic about the future of DynAPI.
I'm having trouble with (what I believe is) a memory leak in dynapi.js at
line 106:
f.onunload = function() {
//alert('hi');
for (
> You are using the latest release, right?
Yep.
> There were memory leaks in previous versions (as this.fame
> was not being set
> to null) , I have not had this problem recently.
>
> If so, please submit it as a bug, but also supply a little
> test-code to
> replicate this problem, that we c
directory, if you can.
Your solution does seem logical though.
cheers,
Richard.
- Original Message -
From: "Phillips, Stephen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 16, 2001 11:57 AM
Subject: [Dynapi-Dev] Memory leak
> Immediate a
Immediate apologies if this has been discussed before, but I've searched
both the docs and the list archives.
We have a serious memory leak when using DynApi - this has been tracked to
DynObject.all retaining a reference to every created DynObject, even though
we do want them deleted (by call
.
- Original Message -
From: "Bogdan Pietroiu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 27 June, 2001 17:32
Subject: [Dynapi-Dev] memory leak
> why in IE the simpe action of draging a layer
> causes memory leak's ?
>
___
smime.p7m
why in IE the simpe action of draging a layer
causes memory leak's ?
smime.p7s
Sent: Monday, February 26, 2001 4:37 PM
Subject: [Dynapi-Dev] Memory leak
> Hi,
>
> My mails has been disapairing into the void while we have been changing
ISPs
> the last couple of days.
>
> So I have missed digest #270 through #282 (both included).
>
> I was wondering
Hi,
My mails has been disapairing into the void while we have been changing ISPs
the last couple of days.
So I have missed digest #270 through #282 (both included).
I was wondering if someone could forward me the digests from the period so I
can catch up.
The memory leak thread seems to have v
15 matches
Mail list logo
