We also had the same issue with the latest chrome browser version 55. To solve this issue, we disabled the hardware acceleration in chrome browser as a workaround.
