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.
The Flash Builder (4.6) profiler shows a current memory usage of about 24000k (so 24MB if I’m not mistaken) for my app, which simply cannot be.
The live object view, however, shows for example that the object with the highest memory consumption, 80 live instances, consumes 119000bytes, or 10% of the overall memory consumption.
That doesn’t really sum up to 24MB now, does it? Can someone explain to me how the profiler calculates the memory consumption?
With the Profiler, there are filters in place by default and that includes hiding certain Flash and Flex classes from the display. Be sure that you’ve removed all filters.
As stated in the comments on the main question, in this case you had not removed the filter for flash.display; meaning that those classes were not displayed in your class list, yet their memory usage were still calculated in the memory usage.