Comment #7 on issue 19342 by rvar...@chromium.org: Cache not cleared automatically. http://code.google.com/p/chromium/issues/detail?id=19342
Thanks Joe, This may be related to fireguard1. The warning inserted by fireguard is concatenated with the resource ETag: Warning: 113 fireguard1 Some of this information has not been updated in the past 24 hours. ETag: "18e6-46dba56e47500" We may have a bug that causes that to happen, or the firewall may be mashing them together sometimes. There is a fix that has not been merged to the stable branch that could be causing this (rev 18774). If you are familiar with wireshark or similar tools we could try to see what the server is sending when we fail to use the proper css. Another option could be to use a build that includes the potential fix and see if you can reproduce the issue. You can download a recent test build from http://build.chromium.org/buildbot/continuous/win/2009-08-17/23547/chrome-win32.zip just copy the contents somewhere and run it from the command line specifying a different profile: chrome --user-data-dir=c:\my_temp_profile This step is important because otherwise you will make your regular installation unable to work afterwards (this is a newer version and the old one will not understand changes made to the profile). Another option would be to switch your installation to the Beta channel (downloading the channel switcher)... but this is a one way trip. -- 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 -~----------~----~----~----~------~----~------~--~---
