Forum Discussion
sha
9 years agoContributor
Does anyone know if this has been fixed in the latest release (or the one before)? I also experience this a couple of times a week and consider upgrading to a newer version (for this reason among others) if it is fixed.
I mostly see it in the beginning of the test when starting up the browser, especially when running virtual mobile browsers (this could also be due to the fact that this involves starting Chrome right after it was closed).
/Søren Harder, QA/Test, Zmags