Tapestry 5
  1. Tapestry 5
  2. TAP5-1110

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

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development