Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
Adobe Flex SDK 4.1 (Release)
-
None
-
None
-
Affected OS(s): All OS Platforms
Language Found: English
Description
Steps to reproduce:
1. Export a release build of the SubApplication project attached
2. Copy the output SWF into the src directory of AIRSWFLoader
3. Export a release build of AIRSWFLoader
4. Launch AIRSWFLoader
The application will cycle through loading and unloading the SubApplication.swf until you quit, it will also create a log file in the app-storage directory with the format log_mp_[value of loadForCompatibility]_[remote|local].txt . Where remote | local is if you are loading a remote SWF or some deliver in app:/ .
5. Observe the log file ( attached log_mp_false_local.txt ) the memory usage, reported with System.totalMemory, levels out around 20mb, this is "expected".
6. Launch AIRSWFLoader from the command line: "AIRSWFloader true"
7. Observe the log file ( attached as log_mp_true_local.txt) the memory does not stabilize and continues to grow
8. Deploy SubApplication.swf to some "remote" http host.
9. Launch AIRSWFloader from the commane line: "AIRSWFLoader false http://[yourserver]/SubApplication.swf 10000
( the two new params are where to load the swf from and a new timer value for loading and unloading, for more info check the txt file in the AIR app)
10. Observe the log file ( attached as log_mp_false_remote.txt ) the memory does not stabilize and continues to grow
11. Launch AIRSWFloader from the commane line: "AIRSWFLoader true http://[yourserver]/SubApplication.swf 10000
12. Observe the log file ( attached as log_mp_true_remote.txt ) the memory does not stabilize and continues to grow
Actual Results:
Step 7, 10 and 12.
Expected Results:
The output in each log file should hit some plateau similar to the output in step 5
Workaround (if any):
None, or totally change your loading strategy which is impractical.