I am trying to get the word out about this problem. The Chrome guys naturally want to push the bug responsibility to DisplayLink people. It's probably best if BOTH camps are aware.
See the bug report at:
http://code.google.com/p/chromium/is...tail?id=172018