+zhenw: maybe related to tab loading experiments?

saturninlepoulet@, could you attach a NetLog of the issue? Please follow the instructions here:
https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Here is log file. 
During saving log session, google.ca and www.m2assurance.com were trying to load. It tooks several minutes to get content

Deleted: chrome-net-export-log.json 1019 KB

chrome-net-export-log.json 1019 KB View Download

Thank you for providing more feedback. Adding requester "wangyix@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The requests seem to all be stuck just before URL_REQUEST_DELEGATE somewhere:

(id:481)
t= 15237 [st=     0]    URL_REQUEST_DELEGATE  [dt=0]
t= 15237 [st=     0]   +URL_REQUEST_START_JOB  [dt=173244]
                        --> load_flags = 37120 (MAIN_FRAME_DEPRECATED | MAYBE_USER_GESTURE | VERIFY_EV_CERT)
                        --> method = "GET"
                        --> url = "http://www.m2assurance.com/"
t=187444 [st=172207]      URL_REQUEST_DELEGATE  [dt=0]
t=187444 [st=172207]      HTTP_CACHE_GET_BACKEND  [dt=0]
t=187444 [st=172207]      HTTP_CACHE_OPEN_ENTRY  [dt=1]
t=187445 [st=172208]      HTTP_CACHE_ADD_TO_ENTRY  [dt=0]
t=187445 [st=172208]      HTTP_CACHE_READ_INFO  [dt=2]
t=187447 [st=172210]     +HTTP_STREAM_REQUEST  [dt=19]

There are a few SW ones, which is usually a solid default assumption, but they appear to be blocking on the fetches rather than the other way around. It's hard to be sure what all happens between URL_REQUEST_START_JOB and URL_REQUEST_DELEGATE since Start may be blocked by, e.g., Service Worker. Short of that, the only thing I see in between is the cookie lookup.

+rdsmith, is it possible some recent changes caused the cookie store to be really slow or something?

+chrisha -zhenw

There's a known problem (issue 477409, also related issue 809199) where loading the cookie store is incredibly slow because, we believe, of some interaction with the OS crypto primitives.

saturninlepoulet: When you say "Save startup tab", what precisely do you mean?  Are you using "Save Page As..."?  Or Menu Bar -> Chrome -> Preferences -> On Startup -> Save a particular set of Tabs?  Or something else?  As much detail as you can manage here would help.

(I may need to ask you for a chrome://tracing profile on startup, which would, I think, rule in or out the known problem I reference above, but that looks like a hassle, so I want to try and repro first.)

Hi,

Startup tab are refering to ones saved in user preferences and that will be automatically open when Chrome start.
Please see attachment screenshot
I will attach a tracing logs ASAP

Thanks

Deleted: startup.JPG 26.2 KB

	startup.JPG 26.2 KB View Download

Please found attached json : that's tracing export

Deleted: trace_tracing.json.gz 3.9 MB

trace_tracing.json.gz 3.9 MB Download

Thank you for the trace!  It confirms my hypothesis that this problem is being caused by veeerrrrry slooooowwww loading from the cookie backing store.  Long wall duration, short CPU duration, suggesting blocked in some OS call.

Before I jump to the assumption that it's the same root cause as issue 477409, let me just check the other obvious possibility.  Is your chrome profile on a network share, or is it a local disk?  If a network share, what kind of performance do you see reading files from that share outside of Chrome?

Indeed Chrome profile is in a 10Gbps network share but performance are fine for read/write operations of any files outside Chrome. Browsing file in explorer is fine too. We did not notice performance degradation at this level.

-chrisha

I just spent some time digging through our UMA statistics, and sadly, at the 95%l Windows users are waiting an average of five seconds for startup cookie loading to complete and let them access their web site (this is the time the requests are waiting; total DB loading time at the 95%l is closer to nine seconds).  So your experience is, sadly, not extremely unusual.

Having said that, I wouldn't mind doing some diagnosis about why your machine is doing this, in hopes that that might guide how to fix this for more people.  Would you be willing to reproduce this problem, wait until everything clears and the startup tabs actually do load, then visit the URL chrome://histograms/Cookie, cut & paste that into a file, and attach it to this issue?

Thanks very much for all your help.  I'm not certain if I'll be able to figure out how to fix this with the tools we currently have in Chrome, but let's see how far I can get.

Please found cookie file.
Note : I don't know if that's related to cookie but here again, I wait for ~110 seconds before to get page content for two distinct web site...
Usually, that's 2 or 3 seconds like any normal browsing.
Thanks!

Deleted: cookie.txt 19.5 KB

cookie.txt 19.5 KB View Download

c#15: Thanks!  I'll take a look.

One question: Are you saying that normally chrome startup doesn't take very long (before your tabs load) but that sometimes it takes a very long time (up to ~110s)?  And confirming: this particular cookie.txt file is an example of the 110 seconds?  

Thanks again!

Well, before update Chrome startup (including tabs load) was pretty quick like everybody would like in normal condition (few secs overall).
Since update, Chrome starts is fine but tab load IS the process that needs a lot of time (up to 110s).
Cookie file is the one I got after all tabs finaly loaded. I hope you will be able to discover the reason !
Thanks!

Do you have Trend Micro installed by any chance? There was another report with similar behavior, but it only showed up on machines with Trend Micro.

No but there is McAfee Antivirus 

Before you asked, yes, I tried to disable antivirus protection to see if it might affect.
But even with antivirus disabled, content is very slow to load in tabs. So I will say that McAfee is not blocking or slowing down tabs load
Thanks!

Unable to reproduce this issue on reported version 64.0.3282.140 using windows 10 with steps mentioned below.

1. Installed 64.0.3282.99 and saved startup as Amazon.com and facebook.com.
2. Upgraded to 64.0.3282.140 and opened chrome -- observed chrome opening with saved start up pages. Attaching screencast for reference.

Could someone from dev team please have a look at comment #19,#20

Thanks!

Deleted: 809178.mp4 1.9 MB

	809178.mp4 1.9 MB View Download

Just realized Windows version was automatically reported here from my laptop... 
But issue we are facing of is happening in Windows Server 2012 R2 actually.
Sorry to mention this just now

FYI : same issue happened if profile is stored in network share of locally

As issue is not reproducible from TE end, could someone from Internals>Network>Cookies team please help in triaging this issue further.

Thanks!

Adding label "TE-NeedsTriageHelp" as this isn't consistently  reproducible from our end. And requesting some one from dev team to have a look into this issue and help in triaging it further.

Thanks!

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.