Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory leak in ConcurrentReferenceHashMap [SPR-11440] #16066

Closed
spring-projects-issues opened this issue Feb 18, 2014 · 0 comments
Closed

Memory leak in ConcurrentReferenceHashMap [SPR-11440] #16066

spring-projects-issues opened this issue Feb 18, 2014 · 0 comments

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Feb 18, 2014

Phil Webb opened SPR-11440 and commented

The restructureIfNecessary method in ConcurrentReferenceHashMap can add new entries Reference objects that have been cleaned.

It appears that relying on ReferenceQueue alone is not enough to ensure that entries get removed. An entry that has been cleaned but somehow doesn't appear as a pollForPurge entry will be continually re-added with a null reference.


Affects: 3.2.7, 4.0.1

Issue Links:

  • #16021 memory leak in class org.springframework.core.ResolvableType
  • #21532 ConcurrentReferenceHashMap does not enforce visibility of cached EntrySet

Referenced from: commits 2b4c81e, 09c5720

Backported to: 3.2.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants