Tapestry holds onto the verbose descriptions of component class 
transformations, causing a memory leak
------------------------------------------------------------------------------------------------------

                 Key: TAP5-1110
                 URL: https://issues.apache.org/jira/browse/TAP5-1110
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.2.0
            Reporter: Howard M. Lewis Ship
            Priority: Minor


As noted, since they are logged, there's no advantage to keeping them in 
memory. Further, the new approach to class transformation in 5.2 means that 
component class transformation is more uniform and less hard to debug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to