Shawn Yang

Nope, this issue is still not resolved. It should be more clear that how to implement this feature than before, since our xlang serialization protocol has been formulized: https://fury.apache.org/docs/specification/fury_xlang_serialization_spec/

> I have no idea now,Could you offer me with more details about the resolution?@chaokunyang Hi @heliang666s , are you still working on this? The protocol details can be found...

If we remove it, those classes will never be collected. In some hot-loading classes scenarios, it will may cause class leak

Maybe we can resolve this in another way. Like let users call Fury to clear classes explicitly. In this way, we can remove those weak/soft values

> > If we remove it, those classes will never be collected. In some hot-loading classes scenarios, it will may cause class leak > > I see it could be...

The value may have strong reference to key, so the key are always strong reachable, and it' will never be taken as weak. The thing here is that Fury will...

How about removing weakkeys & soft values, we can make `org.apache.fury.util.LoaderBinding#clearClassLoader` as a method in `ThreadSafeFury`, and let users to clear classloader explicitly. Then we can remove all weak/soft values...

> It is a simple way and users mostly time need't to take this method. if for may way, I'd like clear `Fury#ClassLoader`, set ClassLoader when `gerFury()` and clear classLoader...

@Munoon Seems this is a bug introduced in #1553 > ok, I was able to reproduce a somewhat similar. And it is also similar to the #1325 > > now...

> > @Munoon Seems this is a bug introduced in #1553 > > Agree. I'm feel sick a bit right now, so I will take a look a bit later....