Thanks guys. Interesting stuff.
I read through the thread about moving/resizing Chrome's temp cache, but it left me wondering... Is Chrome's cache size limited to a size so small that there are files being dropped as new files are downloaded, or is it "open-ended" which would allow it to grow to an unmanageable size?
On one hand - it mentions in the article that the concerns from Chrome users are that this large size can result in fragmentation, which may become an issue, hence the desire of some to move it's entire cache to a different directory [away from the main (C:) drive].
On the other hand - there are concerns that Chrome finds it necessary for files to be dropped to make room for "newer" downloaded files...
I installed/used Chrome yesterday. First round I played was "relatively flawless"... smooth meter... steady screen graphics... stable loading... THEN everything went bonkers during the second round. :/
Once, in multiplay, suddenly I got a "White Screen" disconnect before any of us got a chance to even tee-off on the First hole. This killed the round for the three of us. Then...
I started receiving MEGA "load errors" that caused Quit/Saves of my rounds. Even after closing down the browser, performance steadily went downhill with frequent meter stutter, jerky ball flight/roll and avatar motion (especially on the greens), and slow-loading of screen graphics.
I don't know whether these problems were related to Chrome's cache-size, or not, but I found it interesting that they showed-up AFTER a smooth round, and that they grew in intensity and frequency as I continued to play. Interestingly, at one point, even though the screen graphics were deplorable, the swing meter stabilized, giving me a stutter-free round.
I should also mention that Flash10.1 was "delivered" with my Chrome d/l, so IT could be compounding issues... I intend to revert back to 10.0 today to see if there's any differences with it.
Oh... do Chrome users routinely (before or after each game session) clear Chrome's temp cache?