Check your event listeners because if you're not using weak references
then the garbage collector won't remove it. Disregard if you already
knew that one :)
On May 5, 2009, at 7:58 AM, "Gregor Kiddie" <[email protected]>
wrote:
Hi all,
I’m trying to work out where a memory leak is occurring in our appli
cation (putting me into Jeff’s hell from last week).
When profiling the app, it claims there is still a back reference to
its parent on the display list (even though I remove it!) at
[child0]. When I debug the application, the child is removed as I’d
expected, and the children array is empty.
So which one is lying? The profiler when it tells me there is still
a back reference to the parent as [child0] or the debugger when it
tells me the child has been removed…
Gk.
Gregor Kiddie
Senior Developer
INPS
Tel: 01382 564343
Registered address: The Bread Factory, 1a Broughton Street, London
SW8 3QJ
Registered Number: 1788577
Registered in the UK
Visit our Internet Web site at www.inps.co.uk
The information in this internet email is confidential and is
intended solely for the addressee. Access, copying or re-use of
information in it by anyone else is not authorised. Any views or
opinions presented are solely those of the author and do not
necessarily represent those of INPS or any of its affiliates. If you
are not the intended recipient please contact [email protected]
mlmsg #ygrp-msg p a span.yshortcuts { font-family: Verdana; font-
size: 10px; font-weight: normal; } #ygrp-msg p a { font-family:
Verdana; font-size: 10px; } #ygrp-mlmsg a { color: #1E66AE; }
div.attach-table div div a { text-decoration: none; } div.attach-
table { width: 400px; } -->
