We see the same thing. But we can trigger the issue in different ways. This started to happen when the browser updated. We tested rolling back to a previous version of Chrome and this seem to work.