Ok, so I've modified the code to eliminate JabbyPanda's DataField4 component and creat mx:DateField controls instead.
Modifying the steps so that I create and remove a DateField before taking snapshot, then doing it again I still get the following stuff loitering: http://i629.photobucket.com/albums/uu19/drevans112/Allocate/Profiler-Add-DateField-Controls.png Surely the basic DateField is leaking. Alex Harui wrote > The first time you run code, it can create new Class and Function objects. > I would probably create and remove once, then take a starting snapshot. > If the component is leaking, it usually will show up in subsequent > snapshots, unless there is some first-time initialization code. > > The class and function objects shouldn't cause leaks: they are tied to the > SWF that brought them in. I'm a bit surprised that two managers were > instantiated, but I don't know the code well enough OTOH to say that it is > a problem. > > -Alex -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p8003.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
