Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Adobe Flex SDK 4.0 (Release)
-
None
-
None
-
Affected OS(s): All OS Platforms
Affected OS(s): All OS Platforms
Language Found: English
Description
Steps to reproduce:
1. Attached is the project [sample app] which shows the issue.
2. Run the application . Click on the button load Module .
3. Check the profiler , it will show 1 instance of TextInput [name of the module being loaded]
4. Now click on the UnloadModule button , run the GC in the profiler. We'll see the instance gone down to 0.
5. Now click on the loadModule button, set the focus on TextInput and then unload.
6. Run the GC, instance of Module still hangs in memory.
Actual Results:
Module is not getting garbage collected fine when unloaded.
Expected Results:
Module should be GC'd when unloaded.
Workaround (if any):
I have tried the workaround, of setting the focus on any other text control outside of the module , just before unloading, then the module would be GC'd.
But this works only when somebody just clicks on that text control, not if someone types inside the text control . If one types some text, leaves the focus there and then unloads the Module, workaround fails and module instance is still there in memory even after running GC.
Workaround code is included but commented in application.