[jira] [Commented] (FLEX-33062) mx.managers.PopUpManagerImpl.mx_internal::hideModalWindow() ignores destroy flag if CSS style modalTransparencyDuration is set to 0

["Christoph (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLEX-33062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820071#comment-13820071 ] 

Christoph commented on FLEX-33062:
----------------------------------

Phew! Took me a while to find this bug description. I was hunting popup leaks, and this was a kind of side quest. At least this one is easily worked around:

Always use at least 1 millisecond in modalTransparencyDuration!

> mx.managers.PopUpManagerImpl.mx_internal::hideModalWindow() ignores destroy flag if CSS style modalTransparencyDuration is set to 0
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-33062
>                 URL: https://issues.apache.org/jira/browse/FLEX-33062
>             Project: Apache Flex
>          Issue Type: Bug
>         Environment: Flex 4.5.1; Flex 4.6.0
>            Reporter: Alex Harui
>              Labels: memory_leak
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> mx.managers.PopUpManagerImpl.mx_internal::hideModalWindow() ignores the destroy flag if the CSS style modalTransparencyDuration is set to 0. In this case, the popup manager creates a memory leak. When destroy is set to true, it only sets the visibility of the modalWindow to false instead of removing it from its parent.
> The algorithm for removing the modal window from its parent is implemented in mx.managers.PopUpManagerImpl.fadeOutDestroyEffectEndHandler(). This code probably has to be moved into a separate function and either be called directly from hideModalWindow() when destroy is true and modalTransparencyDuration is 0, otherwise from fadeOutDestroyEffectEndHandler().



--
This message was sent by Atlassian JIRA
(v6.1#6144)