I have the same issue. For me this workaround was succesful: https://code.google.com/p/chromium/issues/detail?id=370022#c13
It amounts to enabling hardware acceleration in Google chrome (instead of disabling), by typing chrome://flags in address bar and "Enable" the "Override software rendering list". See http://www.webupd8.org/2014/01/enable-hardware-acceleration-in-chrome.html for details.
Also starting google-chrome with the flag --disable-gpu remedies the issue.
Which of the two approaches should be preferred?
I have the same issue. For me this workaround was succesful: /code.google. com/p/chromium/ issues/ detail? id=370022# c13
https:/
It amounts to enabling hardware acceleration in Google chrome (instead of disabling), by typing www.webupd8. org/2014/ 01/enable- hardware- acceleration- in-chrome. html for details.
chrome://flags
in address bar and "Enable" the "Override software rendering list". See http://
Also starting google-chrome with the flag --disable-gpu remedies the issue.
Which of the two approaches should be preferred?