andrewl102

Also as far as I'm aware there are no actual builds or any other factors involved in the patching, unless they somehow effect the hash of the original source :...

Correct hash is 450241a06a439cd226c9e9cf5cf634d7

The issue is caused by the clnames fields in FSTStreamEncoder and FSTStreamDecoder. Replacing this section of code: ```clnames = (FSTClazzNameRegistry) conf.getCachedObject(FSTClazzNameRegistry.class); if ( clnames == null ) { clnames =...

Well perhaps we should try to convince him to accept https://github.com/RuedigerMoeller/fast-serialization/pull/254 or better yet provide a more performant fix :P

See also https://github.com/RuedigerMoeller/fast-serialization/issues/235 : multithreaded access has issues if the classes aren't preregistered. I worked around this by providing a special `FSTObjectOutput` that tracks all classes and ensures that preregistration...

Have you tried to see what happens if you preregister each of the classes? It might be the same issue as https://github.com/RuedigerMoeller/fast-serialization/pull/254 / due to https://github.com/RuedigerMoeller/fast-serialization/issues/235, potentially multiple threads are...