This is a known bug of Chrome. You can find more info at https://bugs.chromium.org/p/chromium/issues/detail?id=1151295 and https://bugs.chromium.org/p/chromium/issues/detail?id=1151531 .
We have found a workaround and it will be in the 3.3.1 release.