Closed Frotty closed 6 years ago
That is a good catch! I wonder if I should cache the instance forever, or put it in a WeakReference
and use it while it is available.
Thanks for the fix! When will you release the next version?
Mid oct at the latest
Just for curiosity, was this causing performance issues for you? I assume it was the reflection invocation of newInstance
in the class
Yes, gson already creates many classes. With fire and all my stuff enabled it got up to millions of instances, Many of those were the exclusion strategies - something I couldn't really fix. Is there a snapshot i can use to test if it's fixed?
No snapshot, but you can clone this repo, checkout branch v1.8.0_exclude-by-value-singleton
, change the pom version to whatever you want, do mvn install
and then use that version in your code. Maven should resolve the dependency locally
Still waiting on that 1.7.3 release 🌴
It's coming out tomorrow
julman99 commented 4 days ago It's coming out tomorrow
😢
I am terribly sorry for the delay. Just released version 1.8.0 and it contains the fix for this issue. Can you confirm you see an improvement?
Hi I think it's fixed but I can't test it right now because my profiler license expired.
Thanks again. I forgot to close.
Hi, is there a way to make classes that extend ExclusionByValueStrategy singleton? I profiled my app and the ExcludeLogic Class apparently gets created every time an object is being serialized, when there is really just one instance required.