Comment 16 for bug 1696965

« The official google chrome release on the same configuration is not affected, so this problem is specific to our chromium-browser packages. »

This is in fact not true. While it happens less often, I've been able to reproduce the issue with google chrome launched without any additional command-line flags. Attaching a screenshot.