[TAP5-1710] AssetSource service can retain large numbers of Asset and Resource objects

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3, 5.2
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 19/Oct/11 23:57
• Updated: 20/Oct/11 02:21
• Resolved: 20/Oct/11 00:33

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.