Hi team,

I have been working on FLEX-34230 (StageText skins prevents garbage collection 
of component with TextInputs and TextAreas)
and it appears that GC is prevented by the internal pool of StageText used in 
StageText-based skins (precisely in old StyleableStageText and new 
ScrollableStageText).

Apparently, the purpose of this cache pool is to avoid creating a new StageText 
if one with the same characteristics is already in the pool (and returning that 
one).

Does someone know why this pool has been introduced ?  is it to improve 
performance because StageText allocation is slow ?

I mean, maybe if the reason for it is not valid anymore, the easiest way to fix 
that would be simply to remove the pool, and create a new StageText everytime 
time one is needed.



Maurice

Reply via email to