On Mon, Aug 31, 2009 at 12:12 PM, Mark Mentovai <m...@chromium.org> wrote:
> HTTP resource loading shouldn't be on the browser's main thread. This
> only applies to DOM UI resource loading, chrome: and chrome-internal:.
> That stuff gets funneled through the browser's main thread for things
> like profile and theme access.
OK, I'll rephrase: *something* is blocking the main thread (beachball
cursor, can't scroll, etc.) for multiple seconds at a time for pages like
iGoogle that require lots of HTTP requests. I've been assuming it's http
fetching, since the status line says "waiting for xxxx...". But if that's
not it, something else is.
--Amanda
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
