Java - Random timeouts due to


Ok my head is spinning…

What I see is that by commenting out the System.err.println lines from @Tiramon code, the code no longer times out.

@ThomasNicoullaud Would be good to test your code without any System.err (in case you have some debug in your code). Either it solves the problem too and we have at least one lead. Or it does not solve anything and what I see with @Tiramon code is due to something else to be found…

Still, I can reproduce with @SuperNit code, so still investigating.


No change for me, timeout 90% of test run.
(You can try my CR Code. Just put debug var to false line 434).



Same problem for me with Ultimate Tic Tac Toe.
Several timeout checks inside my code, with System.err.println time that exceed the timeout. Each timeout exceeded immediatly quit the method (return).

I have many System.err.println about this timeouts, without any code between them (except method return), and i’ve already experiment (random) deltas above 40~50ms.

Trying to optimize my code to avoid a maximum of garbage collected objects, quite complicated with Monte Carlo TS :disappointed_relieved:

PS : sorry for my english :wink:


I added GC notifications on my GitC code that timeouts everytime, and I had 0 notifications. The code just seems to run much slower than before.


Same problem with Code of Kutulu…
Light code with only parameters reading and a few very simple distances calculation, random timeout.

Appearing that timeout becomes systematic with one “System.err.println(…)”


Can you simply rollback @_CG_XorMode ? It seems that the new version is much worse than the old one for everyone. There is no reason to keep it in this condition.


Indeed. On Code à la Mode, my code is timing out for all matches now although I had no such issue before on this game…


@CG Also to validate that timeouts are due to GC you can test by setting Epsilon-GC (experimental in Java 11).


Any news here?