What steps will reproduce the problem?
1. Create a TabNavigator with 6 Canvas children (there doesn't need to be
anything in them)
2. Open your app in the FlexBuilder memory profiler, or just watch its
memory usage in your task manager.
What is the expected output? What do you see instead?
A temporary spike in memory would be expected, but I'm seeing about 9 megs
of additional memory used (for BitmapData objects) each time I switch tabs.
This means that switching tabs frequently can cause memory usage to
balloon very quickly. The GC will eventually clean up, but it's proven
pretty easy to get memory usage into the 100s of megs. Just keep switching
tabs...
What version of the product are you using? On what operating system?
0.3 FX3/FP9 on XP 32-bit, in IE 8
Please provide any additional information below.
Based on what I read on your blog and in the old source, it looks like
there's a method called destroyBitmapDatum() that's not being called
anywhere. If you could upload the recent source (so I could take a look)
and/or fix this, it would be most appreciated.
Original issue reported on code.google.com by tklan...@gmail.com on 2 Jul 2009 at 10:34
Original issue reported on code.google.com by
tklan...@gmail.comon 2 Jul 2009 at 10:34