[OFBIZ-4222] UtilCache has memory leak if many temporary caches are created

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Trunk, Upcoming Branch
• Component/s: framework
• Labels: CACHE LEAK MEMORY
• Sprint: Bug Crush Event - 21/2/2015
• Assignee: Adam Heath
• Reporter: Philippe Mouawad
• Created: 20/Mar/11 19:31
• Updated: 11/Jan/22 08:49

Description

Since some time UtilCache has been updated to replace the WeakHashMap by a ConcurrentHashMap:
private static final ConcurrentHashMap<String, UtilCache<?, ?>> utilCacheTable = new ConcurrentHashMap<String, UtilCache<?, ?>>();

I think this fix to concurrency issues has introduced a memory leak or at least a much bigger impact on Memory.
Indeed descendent of AbstractCache (particularly AbstractEntityConditionCache, EntityListCache) tend to create many caches that do not need to always persist in time.

The old WeakHashMap handled this by enabling them to disappear while today the Hard ref disables this.

Issue Links

• is related to: OFBIZ-4220 Current implementation of UtilCache has a memory leak if maxInMemory is set