Yes, read that, it was one of the first ones. Gives a reasonable overview on how memory is allocated but doesn't really get down to the details of working with the results Scout gives to locate leaks.
In our application's architecture we have a common framework and then the main application sits on top of this. I had more success getting a very basic application (sitting on the framework) compiling in FlashBuilder and then using the profiler in that so I could fix any framework leaks first. The loitering objects functionality seems a bit more useful (although not 100% correct) and we have found the biggest part of the leak in the framework code using those tools. I cannot use the FlashBuilder profiler for our main Application as it's too big for it to handle. It's REALLY slow and normally crashes after a few minutes. So...... back to Adobe Scout to work out where the memory is going in the application. Is there anything like the loitering objects functionality in FlashBuilder profiler? Alex Harui wrote > Have you read this: > http://www.adobe.com/devnet/scout/articles/scout-memory-profiling.html -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p7853.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
