Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
Adobe Flex SDK 3.0 (Release)
-
None
-
None
-
Affected OS(s): Windows
Affected OS(s): Windows XP
Browser: Internet Explorer 6.x
Language Found: English
Description
Steps to reproduce:
In the test case(see attachment), I have two buttons, one is "Change Data Also Expand" to update the data provider with 1000 nodes and expand the root node, the other one is "Change Data Without Expand" to update the data provider but not to expand. So the only difference between these two cases is whether expand the root node.
Via the memory monitor, you can see if you click "Change Data Also Expand" button, say 10 times, the memory will increase by almost 1MB for each time and will never reach a peak; while you relaunch the flash by refreshing the page and when you click "Change Data Without Expand" button, the memory will kind of fluctuate around a number. So I guess the openItems property of the Tree comopnent has memory leaks issue.
Actual Results:
The memory consumed by Flex application keeps increasing without reaching a peak if expand the root node when changing the data provider of the Tree component.
Expected Results:
The memory consumed should reach some peak and fluctuate around the peak no matter whether expand the items in the Tree or not.
Workaround (if any):
No workaround.