Google Chrome browser shows corrupted content on Mac OS X – DisplayLink Support: "This issue is due to the browser attempting to use hardware acceleration functions not currently available on virtual screens."
I got bit by this bug - disabling hardware graphics acceleration in Chrome, but not elsewhere, fixed the problem, as recommended by DisplayLink.
I wonder why the DisplayLink cannot hook the acceleration calls, and report ion error when applied to their display?
But I also wonder why Chrome does not check the capabilities of the display. Here, the problem is probably confusion, since some of my displays have acceleration, and some do not. Heterogeneity - gotta love it!
Q: why does MacOS expose use of accelerators to apps?
'via Blog this'