Oddly enough, this was only problem on single-processor machines. Dual or more (or hyperthreading-enabled) machines did not have this problem :slight_smile:

Anyway, we’ve isolated and fixed the problem now.

Thanks!
Vlk