Only memory leak I encountered was with use of XML class. The idMap property needed to be deleted explicitly to fix the leak. This was using Flashlite 3.1. (BTW tracing idMap would show undefined - if use ObjectDumper would get a different trace result.) HTH Jim
--- On Sat, 1/30/10, W.R. de Boer <[email protected]> wrote: From: W.R. de Boer <[email protected]> Subject: [Flashcoders] Known memory leaks in FP10 To: "Flash Coders" <[email protected]> Date: Saturday, January 30, 2010, 3:02 PM Hello, I am currently working on an interesting project that has to be able to run as long as possible. But at the moment I can't get it running more two hours after that the FlashPlayer.exe has 100% CPU usages and crawls down the system in such manner the player has to be killed. Now I am trying to use the Flex Builder's Profiler to find any memory leaks but I don't have much luck yet because the Flash Player keeps crashing when being run via the profiler. Now my questions are: (a) Are their any known memory leaks in the FP10 when using: (1) secondary or client SWFs files (main swf > client.swf) (2) playback of video (3) use of client swfs with only timeline-based animations/assets (b) Are their any lists with all the open memory leaks in FP10? (c) Anyone been able to use the listed techniques/features listed in (a) for more then 300+ hours? (d) Would the use of FP10.1 might improve the situation? P.S. If anyone know some people at Adobe who could give me tips or help me, I would love to get introduced. A desperate Flash user, Thanks in advance, Weyert de Boer _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
