that's the old and common Chrome CSS3D display bug (since Chrome 19 and not fixed by Google since then, even after a lot of reporting).
In Chrome 45 Goolge has restricted the WebGL usage, so some devices were falling back to the CSS3D rendering, but with Chrome 46 the WebGL support was relaxed again, so with Chrome 46 (=the current version) it should work again...