6 ms·

thanks – that was exactly the problem and I was able to find the bug with Chrome's responsive inspector mode. Should be fixed now?