Tom Cesko

I just wanted to add that I still have not been able to separate the issue with the time I have. If I find out where the problem is coming...

I was able to debug the issue and found that it comes from: ```java private void org.eclipse.serializer.reference.LazyReferenceManager.Default.updateStatistics() { /* * This method is intentionally not synchronized. * locking the LazyReferenceManager...

Hi, thanks for the efford. I can't share the whole project, but I will try to build a minimal example. Will take some time tho.

Hi again, here is a minimal example including a reference with contains check which is working just fine. Just execute it a few times and the test set will grow....

Am I right that `LazyHashSet#contains()` already works like that? I am currently using an explicit `contains()` before `add()` as a workaround, as shown in the example reference set, which seems...

For the sake of completeness, in case anyone falls into the same trap: This implicitly means that enum values with their default and final implementation of the hashCode() method must...

There actually is a property in the config file (configuration.txt): `webserver-port` You should be able to set the port with that.

Is it possible that this is exactly the same as what I experienced on https://github.com/eclipse-serializer/serializer/issues/122? I've never been able to reproduce the scenario and haven't had time to test further...

I took multiple thread dumps and attached them. I currently got my project running with the reported behaviour. As offered, I have opened a PR, which I currently think will...

Sucks to be me... I'll have a look 👍🏼