Oops. Just realised that the link to the image didn't apply. You can find it at http://imgur.com/ZBHvw
In addition, the code for the views I'm currently looking at that are causing a leak somewhere can be found at:
Thanks again. Looking forward to some help with this matter!
We need to understand more about what you are seeing. Which views are you flipping between? I didn’t see more than two instances of anything. You may need to turn off filters and look at other things like framework classes. Take a couple of snapshots and compare the instance counts. Whatever is growing is related to the problem.
Please try using weak references with event listeners that you are defining:
You can read about weak references in:
Thanks for the tips and advice guys. Actually studying Profiler a bit more closely (and turning off the filters) turned out that bitmap images were the cause of the problem. I removed the stylesheet from the ViewNavigatorApplication MXML - where I had set a background image - and that resolved a significant part of the memory leak, or as it turns out not so much a leak but more a reloading of the background image very time a view was accessed. So I'm going to try a different method of adding a background image.