> Is there a way to verify that the onLoad is indeed > orphaned in the VM memory pool?
Not directly in code. The way we discovered it is that we were writing an app that was designed to stay open for many hours and was loading XML data regularly. Flash's memory usage was going steadily up and up and up even though we were deleting the XML object. We discovered that deleting the onLoad method we assigned did exactly what we expected it to do. Flash's memory usage would go up when the XML loaded, then go back down to where it was before. Best thing to do is open the Windows Task Manager and watch Flash's memory usage to see if you're having memory waste issues. If you're only calling a potential memory wasting thread rarely, call it every five seconds or so instead to speed up the process and see if the garbage collector is working how you expect it to or if you need to review for memory wasting code. HTH, Steven _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
