Given that the issue seems to be observable only in KVM guests, and that it's not going to be fixed upstream in the stable branch: no this won't prevent chromium 59 from moving to -updates. This should happen real soon now.
Given that the issue seems to be observable only in KVM guests, and that it's not going to be fixed upstream in the stable branch: no this won't prevent chromium 59 from moving to -updates. This should happen real soon now.