speachless: I don't think we have a general problem. Mostly because:

1) Fischer's Clock had been introduced many years ago and nobody ever complained about any suspicious behaviour. Yes, there were some complaints but they had been caused by misunderstanding the concept of this feature.

2) No problem of this kind ever happened to me, not even during the test phase. I am sure that a serious anomaly would have been discovered a long time ago.

3) Although I don't have time for a serious and thorough investigation, I've had a quick look at the source code. Everything seems to be normal and as it should be.

So, my best guess is that aaru was unlucky to find a specific combination of parameters that causes the issue he described. Unfortunatelly I cannot provide more information at this moment.