Hello!
I've noticed a huge amount of memory allocations of java.lang.Boolean being made in calls to CGLIB proxies with a primitive boolean in the method signature. Tracing down the issue, I found that the method invocation code uses the new Boolean(boolean) constructor (which has been deprecated for removal since Java 9, by the way) to box the boolean, instead of the more efficient Boolean.valueOf().
It would be nice to fix this small issue.
Hello!
I've noticed a huge amount of memory allocations of java.lang.Boolean being made in calls to CGLIB proxies with a primitive boolean in the method signature. Tracing down the issue, I found that the method invocation code uses the new Boolean(boolean) constructor (which has been deprecated for removal since Java 9, by the way) to box the boolean, instead of the more efficient Boolean.valueOf().
It would be nice to fix this small issue.