Unsurprisingly, the issue persists with 595.71.05, and 580.159.03 is unaffected.
Hi, quick update. The issue persists with 610.57.04 and 595.91.07; 580.178.04 is unaffected.
Do you have any news from the engineering team @scamp1, as far as at least identifying the root cause?
615.71.09 is still impacted as well.