5 ms·

Thanks for the heads up! We're on it! The fix probably came in mid-update and didn't get included in this batch. Rolling out a hotfix for it shortly, though.