Comment #3 on issue 22150 by [email protected]: Create startup tests for mature profiles http://code.google.com/p/chromium/issues/detail?id=22150
I don't anticipate a problem creating a startup test with a profile in hand. Defining a 'mature profile' or finding a profile which exhibits this issue in the wild might be challenging. Some ideas in no particular order: - reuse reliability_tests+urllist to create a profile with many history items - Google support may have access to a donated profile or users reporting this condition - use/add histograms within profile accesses to single out slow-running code paths - other ideas? (code reviews, developer hints/suspicions about where problems could be, platform specific issues?) Before we spend a lot of time on this, it would be prudent to connect with the initial reporters and capture the sentiment here. aka "chrome was fast when first installed, but now it's dog slow" or whatever. -- 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 -~----------~----~----~----~------~----~------~--~---
