[rhauch]

Great the stack trace heloped you to identify quickly the problem. But it's really after more than 20 successive attempts if this information will help also

The stack trace is essential. Actually, I'm surprised that you were able to repeat it as frequently and consistently, because it is entirely a function of how the System.nanoTime() call is implemented on Windows and how frequently the "relative time" used to compute the nanoTime() result.

Regardless, we'll get it fixed. Thanks for your patience.

[badr]

As I told you, the behaviour is normal and we get this exception after more than 20 successive attempts, so in real work it's really rarely when we will get it, but it's always good to get it fixed forever