Amanda Walker wrote:
> Great writeup. There's definitely too much going on in the UI thread. Even
> after the page paints, I'm seeing multi-second pauses while additional stuff
> comes in, where the browser process is unresponsive (example: iGoogle with a
> bunch of gadgets). It's not clear to me why any http resource loading is on
> the main thread at all...
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.
Mark
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
