Hi,

I was unable to reproduce here.

Can you try providing more detail as described by the following instrucations:  https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Thanks for the quick reply!

File attached--just me clicking on the bookmark and nothing happening.

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

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

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

Can you try it in incognito mode? 

Also, can you try disabling the AdBlock extension?

Done, attached. Different computers--one at work disables incognito.

Deleted: Adblock disabled.json 73.3 KB

Adblock disabled.json 73.3 KB View Download

Deleted: Incognito.json 170 KB

Incognito.json 170 KB View Download

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

I'm still not able to reproduce.  In the logs you provided, it appears that the redirect starts correctly, response headers are received, but then the request is cancelled before the response body starts processing.  I don't have a theory yet for why that would be happening.  There are no obvious red flags in the logs.

Any chance you could try BETA to see if it has the same behavior?

I appreciate your looking into it, but it probably isn't worth the hassle of installing beta (which I had considered). I'd rather just try it when the beta goes live--do you have an estimate when that would be? Or can you notify me?

LMK if it could be the net-tech site. I know the manager. But it seemed to be Chrome--I can access fine on IE.

ETA for next stable release is a little over two weeks from now.

OK, thanks, I'll make a note to check again

Able to reproduce the issue on Chrome version 61.0.3163.100. Issue is a regression broken in M61 branch and below are the bisect details for the same:

Bisect Info:
============
61.0.3163.58 - Good Build
61.0.3163.59 - Bad Build

Change Log: https://chromium.googlesource.com/chromium/src/+log/61.0.3163.58..61.0.3163.59?pretty=fuller&n=10000

Unable to narrow down the regression as the issue is broken in branch. Script generating the errors.

Suspecting below changes could be a possible culprits:

https://chromium.googlesource.com/chromium/src/+/31ca337dc58684f9abe527411e7dbc1b81a93f3c

https://chromium.googlesource.com/chromium/src/+/a1f4989b4d6b627346282bfc1431159c8b9eba45

@ tyoshino: Assigning to you, request you to please take a look into it. @ jam: Also cc'ing you can you please confirm if this could be caused with respect to your change.

Tagging with blocker label, please remove if not the case. Issue is observed on Windows, mac and Linux OS.

Yutaka, please take a look.

https://chromium.googlesource.com/chromium/src/+/a1f4989b4d6b627346282bfc1431159c8b9eba45 is reverted as https://chromium.googlesource.com/chromium/src/+/93282fc8594114f26a3aa3406f33a1e39eda6906.

Disabling PlzNavigate resolves the issue.

Thanks for the triage.  This was fixed in  issue 765780 , and the fix was merged to M62 (currently in beta).  As mentioned, this should get fixed on the stable channel when Chrome 62 launches, probably in about 2 weeks.

Thanks for all the investigation!