Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1710

AssetSource service can retain large numbers of Asset and Resource objects

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.3, 5.2
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Reported from a client, the AssetSource service grew to contain 400MB of objects. It seems that this could be a lot slimmer, especially once the application is loaded and running. Use of WeakHashMaps and SoftReferences should allow the JVM to discard what isn't currently needed.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: