Alexander Scheibe created FLEX-34230:
----------------------------------------
Summary: StageText skins prevents garbage collection of component
with TextInputs and TextAreas
Key: FLEX-34230
URL: https://issues.apache.org/jira/browse/FLEX-34230
Project: Apache Flex
Issue Type: Bug
Components: Spark: TextArea, Spark: TextInput
Affects Versions: Apache Flex 4.12.0
Reporter: Alexander Scheibe
Attachments: MobileTextInputGCTest.fxp
In a mobile application with stage text based TextInput and TextArea elements
garbage collection of sub components (e.g. a view) will not occur until another
component with the same number of text inputs and text areas is added.
I would expect the component to be removed from memory (after the next garbage
collection) when it was removed from its parent.
I created a demo app where a window with a text input with a StageTextInputSkin
is opened. Each time the window is opened it will show a different number of
text inputs (7, 5, 3, 1 and 7 again). Using a memory profiler (e.g. Flash
Builders memory profiler) will show that the instances of the window are kept
in memory until the window is opened again with 7 text inputs.
In our real world application this causes a lot of memory to be wasted.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
