Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
Adobe Flex SDK 3.5 (Release)
-
None
-
None
-
Affected OS(s): Windows
Affected OS(s): Windows XP
Browser: Firefox 3.x
Language Found: English
Description
Problem:
Memory hikes up in Windows Task Manager or process explorer private bytes after loading data in charts.
Note:
1) I'm using Flash Player 10.1.53.64 with Firefox 3.6.6.
2) I removed the mx.. from the exclusion list of Profiler. I can see the flex components used are having the same number of instances and same memory. memory does change after launching the application and loading first time the data. After that the memory seems to be stable and I cannot see any increase in instances of flex components.
3) I can see the same behavior on flex 4.
Method:
Attaching a sample Flex application which has a HTTPService collecting data and displaying it in a Datagrid. When profile the application, i cannot see any hike in flex components memory and that seems to be stable once the application is launched and first time the data is loaded. But in the same time when i look into the firefox.exe process in process explorer i can see the (private bytes) memory rising up after every time i click on load data. Here the data is loaded from a static xml file which is called using the http service.
Steps to reproduce the issue:
1) Import the project attached in flex builder.
2) Use the Flex SDK 3.5 (Flex 4 also can reproduce this issue).
3) Run the application and click on load Data button.
4) Run the processExplorer and check the private bytes of firefox.exe process.
5) Click again on load Data and keep doing it and see the change in the private bytes.
Result:
The memory is rising (private bytes) in process explorer for firefox.exe process after everytime I click on load data. Same behavior can be seen in the windows task manager.
Expected:
Memory must rise and come back to normal after reloading of data.
Workaround: NA