[GROOVY-11271] ConcurrentCommonCache causes memory leaks.

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 4.0.7
• Fix Version/s: 2.5.24, 4.0.18, 3.0.21
• Component/s: ast builder
• Assignee: Daniel Sun
• Reporter: cong yang
• Created: 08/Jan/24 03:04
• Updated: 05/Mar/24 01:53
• Resolved: 11/Jan/24 17:32

Description

ConcurrentCommonCache uses a read-write lock to wrap CommonCache into a thread-safe data structure. However, CommonCache uses the underlying LinkedHashMap, which causes conflicts when using the LRU algorithm because the LinkedHashMap.get method modifies the internal linked list. This conflicts with the read lock used by the get method in ConcurrentCommonCache when multiple threads access it. Due to multithreading conflicts, the maximum cache size of 64 becomes ineffective, ultimately causing memory leaks. Additionally, we have already encountered memory leaks in our production environment.

Issue Links

• links to: GitHub Pull Request #2030