Comment #16 on issue 16694 by ChuckSomer: Chrome freezes requiring hard reboot http://code.google.com/p/chromium/issues/detail?id=16694
As I posted on my own thread on this issue, I seem to have progress (not sure why)... ___________________________________________________ ChuckSomer has posted an answer to the question "Chrome causes Windows hang requiring hard reset on some systems": OK - I don't know what changed. I doubt Google would have pushed out a fix without changing the version number - that makes it much too hard to keep track of an already-hard-to-manage complex project. Now as I mentioned earlier, I have McAfee VirusScan Enterprise Workstation (version 8.5.0.781) and it is one of several things on corporate computers within Eastman Kodak that are remotely administered by corporate IS and over which I have no control. (I can't turn it off.) I am still running Chrome 3.0.195.27 (same as on10/21 when I posted above that it still locked up) HOWEVER, I have had a many-many tabs session going continuously since yesterday morning and NO LOCKUP! It is possible the McAfee software had a version change, or a change in policy as to what runs when, pushed out by corporate IS on or about 10/26, because on one of my machines (not this one, but all are on the same network) beginning the morning of 10/27 the McAfee behavior was much different. Scanning frequency and/or thoroughness apparently changed because I began having performance problems on that machine every morning. The McAfee scanner would be running when I came in (having apparently started some time overnight) and would put the machine on its knees, scanning at high priority, consuming nearly all available CPU power. Also a Kodak installed-software management tool which inventories software on the machine was also running, consuming the rest of available CPU cycles. This is the only change since 10/21, so it may relate to the hangs. As I may have mentioned earlier, I routinely run Chrome at home (Vista Home Premium) with sometimes 20 or more tabs open, with never so much as a temporary freeze, let alone any real lockup. Maybe the situation has righted itself - who knows. I will continue to use Chrome heavily on this machine now, to see if it is truly "cured". I'll post whatever the results of that turn out to be. Cheers, Chuck Somerville Eastman Kodak Company Dayton Ohio chucksomer AT gmail.com chuck.somerville AT kodak.com -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
