Comment #4 on issue 19671 by [email protected]: high cpu usage while waiting server response http://code.google.com/p/chromium/issues/detail?id=19671
lilwong: If you're able to crash chromium using a flaky 3G connection, please send us a repro case. We definitely want to fix crashes. If you know how to repro it, also try doing it with google-chrome, because then we'll get stacktraces. Send us your client id (it will print to stderr [so, yeah, run it in a terminal] when google-chrome crashes) and then we can match it up with our crash reports. Can you also try to see if catinsnow's suggested repro steps (using unreachable urls like http://2.3.4.5) also cause the same cpu utilization that you're reporting? If so, then I think that my explanation stands (tabstrip is doing a lot of rendering because of the loading animation). Otherwise, then perhaps there's something else going on. Also, can you be specific about the cpu usage? When you run top, are you seeing the main browser process (the parent/ancestor process of all the other processes [zygote, renderer/etc]) consume 100% of cpu usage? Or are you seeing a renderer process consume the 100% of cpu? How are you determining this...via top? -- 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 -~----------~----~----~----~------~----~------~--~---
