Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Hi I’m looking into the issues to expect if the Flash Player (version 10) is run over a long period of time, say 24+ hours.
I know that the player has issues with not performing garbage collection properly, and that the weak listener system is buggy.
I plan on having the flash app started/monitored using a watchdog/sentinal app written in C/C++/C#. So I plan on refreshing the app periodically.
Does anyone have recommended practices for running a flash player over that sort of time scale?
Memory leaks are probably the worst. If you manage to make an app run on a 100% stable memory level for 1 hour it should also run for 24 hour and more (if its activity is stable as well).
Flex’s profiler is nice to look up for leaks and uncollected items …