1. Why doesn't he show assets (bitmaps, fonts, ... the things that take the most RAM)? Profiler reports 6 megs, but System.totalMemory reports 40 megs. No other SWF is open on the system beyond that one (so as not to pollute System.totalMemory accounting for multiple SWF's).
2. I had some XML accounting for 150 megs of 190 megs, yet the profiler didn't show it; said 21 megs. I ran garbage collection multiple times in the profiler, but it still stayed around. Why isn't it picking this massive chunk up? 3. What are "Method Closure"; event listeners? 4. Running code in Flash, I can confirm from both viewing memory via System.totalMemory + having a timer that traces out a message on every tick that a SWF is in fact unloaded from a Loader in Flash Player 10. Running this code in the profiler shows the Loader never unloading (yes, I'm compiling for 10 and yes I'm using unloadAndStop; remember, same code). The profiler claims Loader still has it's instance around and the timer doesn't die with his weak listener... but does running in Flash.
