MemoryLeak caused by UriTemplate cache
See original GitHub issueI noticed that UriTemplate.CACHE
is never evicted. With recent changes it seems that any Link
instance holds a template whether the href is templated or not. So, if an API exposes a lot of links with concrete URLs that will create a lot of cache entries when parsed into Link
s and underlying UriTemplate
s .
This led to OutOfMemoryError
s eventually in our application.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Will Spring Cache cause memory leak issue? - Stack Overflow
It means when no caching library, like Redis (using Spring Data Redis, for instance), is detected on your Spring Boot application classpath. In ......
Read more >ChangeLog - Spring
#1118 - MemoryLeak caused by UriTemplate cache. - #1116 - Refine factory methods and nullability checks for RepresentationModel types.
Read more >PM84305: OUTOFMEMORYERROR CAUSED BY MEMORY ...
When an application is designed such that every request for the same static content is unique, it consumes more memory to cache the...
Read more >Avoiding memory leaks with Spring Boot WebClient | bol.com
What caused this memory leak? ... “[w]ith this solution the WebClient doesn't know the URI template origin, as it gets passed the final...
Read more >Fedoraproject Fedora : List of security vulnerabilities - CVE Details
An attacker could potentially exploit the vulnerability to cause a denial of service, ... after allocating memory, which may cause a memory leak....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@odrotbohm That commit is on
master
, which is1.1
. Still needs to be backported to1.0.x
.Should be available in 1.0.2.BUILD-SNAPSHOT in a few minutes. Feel free to give them a try!