Have you read through my blog post about the profiler? http://blogs.adobe.com/aharui/2008/09/using_the_flex_builder_3x_prof.html
Loitering Objects cannot be used for all scenarios. Sometimes manual comparison is required. Weak references do create "noise" in that you have to learn to ignore them (or remove them) when chasing down the source of a leak. Make sure you set the option to show all back references instead of just "20" or whatever the default is. I've not seen any "bugs" in the profiler regarding weak references. The profiler does not know how to filter out which references are weak. HTH, -Alex On 6/24/13 10:06 AM, "Brett Trotter" <[email protected]> wrote: >Hello, I have what I hope is a quick question for anyone. We have a quite >large Flex based application with multiple dynamically loaded RSLs. In >profiling the application, we see what appear to be "false flag" weak >references showing up in the loitering objects. We have to go and turn >things off and until we get rid of all potential weak references before we >see the real GC root holding on to the memory. I'd like to think I'm doing >something wrong. Is this something you've seen and either know how to fix >or can confirm it's a bug in the Adobe Flash Builder Profiler?
