Tested the issue on Win 10 using latest stable 57.0.2987.133 and could not reproduce the issue.Could you please review the attached screen cast and let us know if any steps missed from our side.

Deleted: 711616-17-04.mp4 3.7 MB

	711616-17-04.mp4 3.7 MB View Download

This is a link to a video of what happens, sorry for quality but you will hopefully see what is going on. I did this for my antivirus provider but they say the problem I am having is nothing to do with the antivirus software. I could not upload it here as too large. Thank you.

https://www.youtube.com/watch?v=ANbdKsD2wms

Thank you for providing more feedback. Adding requester "sandeepkumars@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

Unable to reproduce the issue on Windows-10,Windows-7,Mac-10.12.4 and Linux Ubuntu-14.04 using chrome stable version 57.0.2987.133 and canary 60.0.3074.0 with the steps mentioned in comment#0.
as100uk@ could you please try in a clean profile without any extensions and let us know your observations if the issue still persists.

Thanks.

I have no extensions running.  I am beyond fed up.  I deplore IE but am having no such issue with IE and am tempted to not use Chrome, even though until now I have used it exclusively and prefer it.  Have you looked at my video to see what is actally happening? I have to do that everytime I open a page in a new tab before it will load? Any suggestions as to what could be doing this if not a Chrome issue? I only have my one profile, are you saying I need to create a whole new one?  I am not PC savvy, hence posting on here for the help of experts :-).  I appreciate you responding and trying to help, thank you.

Thank you for providing more feedback. Adding requester "sureshkumari@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

Is it only links from Google searches that show this behavior?  Could you please create and upload a net-internals log?  Instructions:  https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Tentatively labeling this a network issue.

I attach the log as requested.  Interestingly, once I opened the net-internals page and then did a random search and right-clicked and opened random results, a few opened and a few did the behaviour I have reported ie hang on a white page until time out.

Deleted: net-internals-log.json 11.7 MB

net-internals-log.json 11.7 MB View Download

PS it only happens when using Chrome.  If I search with google using IE it does not happen.

Thank you for providing more feedback. Adding requester "mmenke@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

Thanks for the log!  I'm not seeing any network errors.  The slowest request takes about 4 seconds, which is pretty bad, but doesn't seem to be the source of the problem.

One thing that is weird is random events sometimes take multiple seconds - sometimes DNS, sometimes receiving data, etc.  I wonder if something isn't consuming a ton of CPU time on the IO thread.

When this happens, are other tabs responsive (Can you scroll them, or navigate them to HTTP URLs) without issue?  Does Windows task manager show a chrome process using 1/[number of CPUs]% of CPU time?

Could you gather a trace from about:tracing and upload it?  This will hopefully let us narrow down what's consuming CPU cycles, since it now doesn't look like this is network related.

Thank you for trying to help me.  I will have to do it on PC tomorrow.  

Pages that do load can be viewed while the others are loading and, again, on the pages not loading/white screen if I delete just the https:// at the beginning of the page address and refresh by pressing return on my keyboard, the page loads almost instantly.  I have to do this every time and only in Chrome.  It does not happen on Internet Explorer, pages open via a right click in a new tab immediately with no issues at all.

Thank you for providing more feedback. Adding requester "mmenke@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

(Adding back needs-feedback label as we wait for traces)

Hi, so I went to about:tracing.  There are no directions of what to do and I have no idea what it is or what it is used for so I have not been able to "gather a trace" for you as I do not know how to.  Are there any instructions for using this?

I would also have no idea about Chrome processes in task manager.  There are several in background processes but I do not know what that means.

If it is something to do with my pc why is Google working perfectly in Internet Explorer but NOT in Chrome on the same PC?

Many thanks.

Thank you for providing more feedback. Adding requester "mmenke@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

That's a very good question.  Could you go to record->manually select settings->"Select all" on the left pane ("Record Categories"), click record, then reproduce the behavior that causes the problem?

Also, two other things you could try:
* Disable all extensions (About:extensions), if you have any.
* Try running chrome with --disable-gpu-compositing --no-sandbox and see if that works.  Do not continue to use Chrome with the no-sandbox argument if this works, just want to see if this is an issue launching a sandboxed process.

Sorry for the litany of suggestions, it's just not at all clear what's causing the problem you're running into, and browsers are complicated.

Hi, thanks again for the help, I attach the tracing - I hope it worked.  I must admit the issue did not really happen when I recorded (typical!)  However, some tabs seemed to take a while to load. I have no extensions running - not sure how to see GPU composting and Sandbox but went to chrome://flags and pretty much everything is disabled.

Deleted: trace_tracing.json.gz 22.6 MB

trace_tracing.json.gz 22.6 MB Download

Is deleting 'https://' necessary to cause it to load? Or does the load happen if you just select the URL and hit enter (without deleting the prefix)

I have to delete the https:// if I do that and refresh by hitting enter the page loads immediately.  If I do not do this the page displays a white screen until it timesout/becomes unresponsive.

That trace file looks corrupt (Cut off at the end, I think?) could you please try again?  Thanks!

here you go :-)

This is what was displayed:

ERROR While importing:
RangeError: Inflated gzip data too long to fit into a string (297719515).
    at Function.GzipImporter.inflateGzipData_ (chrome://tracing/tracing.js:4995:201)
    at GzipImporter.extractSubtraces (chrome://tracing/tracing.js:4999:276)
    at Import.createImports (chrome://tracing/tracing.js:1352:112)
    at Task.run (chrome://tracing/tracing.js:2111:13)
    at runAnother (chrome://tracing/tracing.js:2122:160)
    at runTask (chrome://tracing/tracing.js:2086:57)
    at processIdleWork (chrome://tracing/tracing.js:2092:116)
    at window.requestIdleCallback.timeout (chrome://tracing/tracing.js:2080:81)

Deleted: trace_Tue_Apr_25_2017_5.22.38_PM.json.gz 26.5 MB

trace_Tue_Apr_25_2017_5.22.38_PM.json.gz 26.5 MB Download

Matt: I think of "select all" in about tracing as an open invitation to run out of some form of storage space, which is I think what's happening here.

Charles: The question I asked you for curiosity has just gotten a specific bug it's relevant to :-}: Do you know what about:tracing configuration would be likely to show up long-running tasks on the IO thread without blowing memory?

as100uk@: One question while we're trying to figure out the right about:tracing config: for the specific time you saw the problem in the log you attached in c#19, what address was showing it?  An did that log include both the (failed) attempt from the right click and the deletion of https and retry, or just the attempt from the right click?

as100uk@: For about:tracing: Record -> Select None (i.e. nuke everything selected by default) -> Select toplevel, net, and netlog.  Then click "Record", reproduce the problem, and then click "stop".  Attach those logs with specifics as to what address was slow so we can find it in the logs.  

If you're willing, do a net-internals dump at the same time (probably set that up first and stop it afterwards) just so we have the maximum data about one specific example.

Thanks very much for all the help.

(And thanks, Charles, for the pointer.)

"netlog" is a relatively heavyweight tracing category so if the netlog is big then it might make sense to omit that category in the trace. Those three are a fine first attempt though.

Thanks for your help, I will look into doing all this tomorrow.

For the log I attached I did not make any note of the address, I was just opening random pages with a right click - I did not have to delete the https:// (see next para)

The weird thing is that I constantly have to delete https:// for pages to load instantly.  When it happens I open the chrome/trace and do the search/open again and it does not happen - the pages load but just seem to take longer than usual.  It is a pain in the Bu%%!

I have no idea what a net-internals dump is :-)

All understood; thanks for giving it a shot.  

Re: net-internals, I envy you you're ability to purge your mind of non-essentials, since you already gave us one in c#9 :-}.  But instructions for doing a n-i dump are @ https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details .

OK, I tried to do the net_internals, it crashed Chrome.  Reopened and did the chrome://tracing, set up as requested, and hit record.  Did a search, randomly right clicked to open some pages.  The unwanted behaviour happened - I could not note the web pages as only https://www.google.co.uk.....etc is displayed on the pages it happens to.  I went back to tracing to stop recording.  I clicked stop - nothing happened.  I waited for a good several mins in case it needed time to complete the log. Nothing happened, so I guess that "crashed" too!  I attach a screen shot as how the tracing page looked after pressing stop and waiting for it to produce the log (which it did not).  You will note the three tabs on the top right that are still trying to load - each starting https://www.google etc - If I go and delete that https:// and refresh they will all open instantly!

I think there is obviously no quick fix for this.  For the timebeing I will just have to go to another browser as it is slowing me down so much.

Deleted: chrome1.doc 244 KB

chrome1.doc 244 KB Download

well, i spoke too soon the log did appear! Here it is attached :-)

One of the webpages that failed was:
https://www.ukessays.com/essays/health-and-social-care/case-study-abdominal-aortic-aneurysm-health-and-social-care-essay.php

I apologise but I did not get the other two.

Deleted: trace_Thu_Apr_27_2017_8.08.57_AM.json.gz 2.3 MB

trace_Thu_Apr_27_2017_8.08.57_AM.json.gz 2.3 MB Download

Yeah, sorry, I'm at a loss.  From the log you just sent, there isn't anything being particularly active that should result in thread scheduling problems.  From the earlier net-internals log, it looks like a slow network--each of the slow requests I drilled down on was because either of a long delay on a DNS response or a long delay on reading headers or data.  One very random thought is that if there's some firewall/MITM proxy that gets involved when you try to access https, that might explain it (though it wouldn't explain the delayed DNS responses; those don't go over a secure connection). 

But if you're going to switch to a different browser, I doubt we'll be able to do much more debugging on this one.  Thanks for helping us try to figure this problem out.  

If you want to keep digging with Chrome, ping me back and I'll re-open the bug.  The next step would probably be to reproduce the n-i dump from c#9, making sure to capture the reproduction of *both* the slow behavior (from the right click) and the fast behavior (from editing the Omnibox) and sending us both the log and the URL(s) for the link that was slow&fast.