Thomas Heigl

@amodolo: I am using `ClosureSerializer` on OpenJDK 17 for quite a while now. It works fine. Are you sure you are passing the JVM argument correctly? I'm passing the following...

I just ran `ClosureSerializerTest` in Kryo with the following settings: It works fine. The command run by IntelliJ looks like this: ```/Users/XXX/Library/Java/JavaVirtualMachines/temurin-17.0.7/Contents/Home/bin/java --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --enable-preview ......``` How does...

@endlesstian: You can already register all these serializers yourself. They are available for manual registration since Kryo 5.4.0. As for Kryo 6, I currently do not have a release date....

@vyalyh-oleg: Kryo currently only adds an automatic module name. So far, there is no module definition. What is required for add-opens to be restricted to Kryo?

@chrisr3: Thanks a lot for the reproducer! Do you know how we could add Kotlin support to our test? I'd really like to have a unit test when I fix...

Your sledge-hammer fix looks good to me. It's not worse than the other two "fixes" I applied to various generics corner cases. ;) I will merge it after my PR...

Merged. Thanks again @chrisr3!

@JanecekPetr: Ping ;) I'd like to do another Kryo 5.x release in the coming weeks. Any chance you can create a PR with your caching improvements?

@JanecekPetr: I created a PR with caching for the `RecordSerializer` here: #927 Is this the same approach you took? I'm also seeing a 20x speed-up.

Please provide a minimal reproducer for this issue. It's not possible to diagnose the problem from the stacktrace alone.