tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1956) Tapestry.ZoneManager creates memory leaks
Date Fri, 15 Jun 2012 17:50:43 GMT

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

Howard M. Lewis Ship commented on TAP5-1956:
--------------------------------------------

Have you verified these leaks?  I did some work in 5.2 or 5.3 to address this; when Tapestry
removes content from the DOM , it walks the removed DOM elements and clears the attached Tapestry
object, and nulls any function properties it sees. That's supposed to break the cycle.
                
> Tapestry.ZoneManager creates memory leaks
> -----------------------------------------
>
>                 Key: TAP5-1956
>                 URL: https://issues.apache.org/jira/browse/TAP5-1956
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.3
>            Reporter: Jochen Kemnade
>              Labels: dom, memory_leak, patch, zone
>         Attachments: 0001-Fix-memory-leaks-with-Tapestry.ZoneManager.patch
>
>
> The Tapestry.ZoneManager creates a circular reference between the DOM tree and the ZoneManager
JS object. This circle is not broken when the element is removed from the DOM, so it will
not be cleaned up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message