I use Google Chrome in a peculiar way. I prefer Firefox for browsing on Windows because of some add-ons I cannot live without. But I have found Google Chrome perfect for debugging on the Flex/Papervision3d project that I am currently working on – primarily because of it’s per-tab process, responsiveness and generally low overhead nature.
I decided to try out the Windows 7 beta and since I primarily work off my MacBook Pro, I installed the 64bit version on Fusion. Things went swimmingly except for Chrome which just wouldn’t work. I kept getting told off that Chrome “has known compatibility issues” and if I ignored those warnings, Chrome would scream bloody murder even if I touched it lightly.
Add the “–in-process-plugins” switch to the “Target” of the shortcut for Chrome as in the screenshot below.
[That is two dashes before the "in" --in]
You’ll still possibly get those annoying “Has known compatibility issues” warnings but you can choose to turn those off.
Hope this helps.