No - I was working on these errors (and their intermittency) on the weekend, that's why they are still fresh in my mind. It might be that a Chrome update surfaces this problem now more often.