Hi Enoch,
this seems to be related to GPU accelerated compositing (turned on by default with Chrome 15).
Disabling it via command line switch fixes the problem, but that's not really an option with the end users of our google-maps-centered webapp (more so after urging them for months to switch to Chrome because it was way faster ...)
Any hope of an update fixing this? (like, for example, a new chrome build disabling the bugged GPU acceleration?)