Stéphane Nicoll opened SPR-12275 and commented

While doing some investigations on #16021 we discovered that the ResolvableType internal cache was holding a lot of duplicates for simple types (i.e. String, Integer, etc).

It turns out that we are using too much metadata to compute the key when the class has no generic information. so setFoo(String foo) and setBar(String bar) would result in two entries in the cache because the TypeProvider is different.

Affects: 4.0.7, 4.1 GA

Issue Links:

• memory leak in class org.springframework.core.ResolvableType [SPR-11394] #16021 memory leak in class org.springframework.core.ResolvableType

Backported to: 4.0.8