on the basis of your mess. For take care of GC of your Objects...
you have to consider 1) all reference should null to that Objects..
2) U should disp. them by calling from parent.
3) Most important is u have to remove all event Listener from that Object... becoz of event life cycle if event listener is still there then it will live untill appli. end...
other points u know.... so....i think this will help u......
1 person found this helpful
In theory, the Object References view should never show an object with no
back references. There is a chance that the GC did not get around to that
object, but hitting the GC button in the profiler a couple of times
(assuming the app is idle) should guarantee that the mark and sweep took a
look at the object.
If the object is still around after doing that, it might be that the object
is being cached by the Flash Player. There are some issues with AIR apps
where objects that listen to AIR object events don't get their back
references shown. Study the objects in question and make sure that event
listeners are being removed.
Yes I did press the GC button a number of times and I have done a complete review of all the events listeners that we assigned to this object and there is only one which is removed before the object is nulled out. Wouldn't i still see a reference if there was a dangling event listener. To add a wrinkle to my issue, there is some interaction with this object and a third party library so I don't have full visability into all interactions to this object and since there is no references to this object I have no path to follow since I have cleaned up all references.
whatever i suggested, same thing suggested by Flex harUI n he add some imp. points into it... thanks..... Flex harUI.....
Coming to your probl. u tried every thing, Try this last thing, remove the object from the parent by remove child and assign null to parent properties n assign null to child properties of parent object... May be this will help u... but.... as per Flex harUI if AIR stores object in cache then its diff. prob.... May your object refe. using by some shared lib or class so it is storing that in cache or it live through out the life of app.
And in the last reply you written that don't have full visability into all interactions to this object becoz you r using third party lib. So, May be this will help u...
Thanks for reply....