Comment #22 on issue 265 by [EMAIL PROTECTED]: Safe-Browsing feature hogs system http://code.google.com/p/chromium/issues/detail?id=265
Thanks for all the feedback on this issue, we've made progress towards fixing the problem. The latest version of Google Chrome (0.4.154.25) is being pushed to dev channel users, and contains a new implementation of the SafeBrowsing storage system that greatly reduces the amount of disk IO during an update cycle and reduces the amount of time needed to process each update. We hope this will eliminate the browser unresponsiveness that has been reported here. If you'd like to try this new implemention, here's what you need to do: 1. Switch to the dev channel: http://dev.chromium.org/getting-involved/dev-channel/ 2. Get the latest version of Google Chrome by choosing the "About Google Chrome" option from the wrench menu and seeing that it says 0.4.154.25 as the version number. 3. Run Google Chrome with command line flag: --new-safe-browsing You can add the command line flag to shortcut used to launch Google Chrome by: 1. Right click the Google Chrome icon on the Windows Quick Launch bar or desktop shortcut 2. Select "Properties" 3. Choose the "Shortcut" tab 4. Add --new-safe-browsing to the "Target" field after chrome.exe 5. Click OK 6. Restart Google Chrome from the shortcut you just modified 7. Make sure that "Enable phishing and malware protection" is checked (wrench menu --> "Options" --> "Under the hood") Google Chrome will perform a SafeBrowsing update within 5 minutes of launch, and roughly every 30 minutes there after, so you should be able to quickly tell if this new version has improved responsiveness for you. You can go back the older SafeBrowsing system by removing the command line flag. If you decide to try this new version, please let us know if it has fixed the problems you've seen by adding your feedback to this bug report, and thank you for helping us improve Google Chrome! -- 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
