Updates:
        Cc: [email protected] [email protected]

Comment #3 on issue 16581 by [email protected]: Browser unresponsive until  
all tabs finish load
http://code.google.com/p/chromium/issues/detail?id=16581

Just to clarify... am I correct that this is NOT about startup time with  
multiple
tabs, but rather about clicking on links to either "open in new tab"  
or "open in new
window." For example, you might (in an existing tab) open links by  
shift-clcking a
link, or ctrl-clicking a link.

Am I also correct that the problem is that scrolling etc. in the original  
tab is
seemingly blocked while the throbber appears in the top of the  
(undisplayed) pending
tabs?

I'm not especially familiar with the sequence surrounding creation of new  
renderer
tabs... but perchance we are being more liberal about creating new  
processes (rather
than using tabs to hold multiple sites) and that is slowing us down. In the  
worst
case, it would be a bad thing if we somehow blocked the UI thread during  
these
process constructions.   I'm going to cc a few folks in case they're aware  
of any
process count changes that might be having an impact.

We *might* be able to see some evidence of jankiness by looking at  
about:histograms
and seeing if "Chrome.ProcMsgL UI" or "Chrome.ProcMsgL UI" were picking up  
a lot of
samples of events that are taking a looooong time.  I have seen some  
strange stuff
initially in those histograms... so it would be important to see that  
things got
worse when you tried to repro this bug (i.e., we got a lot of long  
samples.  Note
those histograms have times in milliseconds, and hence *should* only have  
samples
that are very short, way under 100ms).


--
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to