When instantiating a config proxy through ConfigProxyFactory, the lambdas that allow access to default methods in the interface are re-created for each proxy object, even though they are only unique to the entire class.
This is normally not an issue, but if a client creates many (in the hundreds) instances of proxies for the same class (for different prefixes, for example) they can end up consuming a large amount of metaclass space.
When instantiating a config proxy through
ConfigProxyFactory, the lambdas that allow access to default methods in the interface are re-created for each proxy object, even though they are only unique to the entire class.This is normally not an issue, but if a client creates many (in the hundreds) instances of proxies for the same class (for different prefixes, for example) they can end up consuming a large amount of metaclass space.