This is the bug you're talking about and I can't wait for it to be fixed up: http://code.google.com/p/chromium/issues/detail?id=29729 You might find a temp solution here: http://www.google.com/support/forum/p/Chrome/thread?tid=3d94...

It's fine here: OS X 10.5.8, Chrome 5.0.371.0 dev.