New issue
Advanced search Search tips

Issue 920255 link

Starred by 5 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome WebRequests Unexpectedly Cancelled

Reported by case...@prodege.com, Jan 9

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
See attached document "ReadMe Chrome WebRequests Unexpectedly Cancelled" for multiple examples.
Also includes a Chrome Extension used for testing.

Simplest example.
Install Chrome Extension Redirect Path. 
Go to Url http://www.tkqlhce.com/click-5897557-12377205?sid=638468599&afsrc=1&context=loyalty and see it doesn't finish. 
Actual Error is net::ERR_ABORTED.
(But no errors in older versions of Chrome)

What is the expected behavior?
Redirects without Error

What went wrong?
See Attached Document for details.
We have a browser extension that relies on the chrome.webRequests API to observe and react to various request life cycle events.

As of Chrome 71, we are noticing an increase in the number of requests that are unexpectedly cancelled between onBeforeRedirect and onResponseStarted, usually associated with a 301 or 302 redirect.

Prior to Chrome 71, these same requests reached onCompleted without error.
The issue remains reproducible in the Chrome beta (72.0.3626.28) and canary (73.0.3665.0) builds.

Did this work before? Yes 70

Does this work in other browsers? N/A
 We see the same lack of 

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version: 

Attached zip has:
ReadMe document with details.
Screenshots
Chromium_Net_Internals logs
Test Chrome Extension to output errors.

PS.
Your bug reporting page has a bug. You can't get past the first 50ish items in the dropdown 'Which Component does this fall under' I wanted to file under Extension API, but the html page won't allow me to get past 'Blink'
 
Chrome_WebRequests_Unexpectedly_Cancelled.zip
8.9 MB Download
Please Change Component to Platform>Extensions>API

Your bug reporting page has a bug. You can't get past the first 50ish items in the dropdown 'Which Component does this fall under' I wanted to file under Extension API, but the html page won't allow me to get past 'Blink'
Labels: Needs-Triage-M71 Needs-Bisect
Components: Platform>Extensions>API
Cc: susan.boorgula@chromium.org
Labels: Triaged-ET Needs-Feedback
casey.c@ Thanks for the issue.

Tested this issue on Windows 10 on the reported version 71.0.3578.98 and the latest Canary 73.0.3666.0 and unable to reproduce the issue by following the below steps.

1. Launched Chrome and added the extension 'Redirect Path' given in document.
2. Navigated to http://www.tkqlhce.com/click-5897557-12377205?sid=638468599&afsrc=1&context=loyalty and opened Devtools -> Console.
3. Couldn't observe any errors on the console page.
Attached is the screen cast for reference.

Request you to check and confirm if anything is missed from our end in triaging the issue.
Also request you to provide a screen cast of the steps followed to reproduce the issue, which will help in better understanding.

Thanks..
920255-M71.mp4
2.2 MB View Download
You must use an extension. The issues is with the https://developer.chrome.com/extensions/webRequest


1. Download zip file from https://bugs.chromium.org/p/chromium/issues/detail?id=920255
2. Extract outer zip
3. Extract Test Extension
4. Navigate Chrome to chrome://extensions/
5. Load Unpacked (make sure you are in Developer Mode)
6. Open Background Page Dev Tools for Test Extension
7. Verify you see message 'redirectTest background page loaded'
8. Open New Chrome Tab
9. drop this url into browser. 
http://www.tkqlhce.com/click-5897557-12377https://bugs.chromium.org/p/chromium/issues/detail?id=920255205?sid=638468599&afsrc=1&context=loyalty
10. End of Screen cast.

11. You can also show with Google Ads. Clear the console log and drop this url into the address bar. https://www.google.com/aclk?sa=l&ai=DChcSEwjrv9uN-97fAhWOymQKHZJ0ANoYABAAGgJwag&sig=AOD64_1_kEE1pw49PKJax5hEuGK47kyNOg&q=&ved=2ahUKEwj52NWN-97fAhWJ11QKHYBVAggQ0Qx6BAgFEAE&adurl=

12. See more details/samples in Word document and Screenshots in download.
WebRequest_Unexpectedly_Cancelled_1.mp4
4.0 MB View Download
Project Member

Comment 6 by sheriffbot@chromium.org, Jan 10

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
casey.c@ Thanks for the update.

Tested this issue on Windows 10 on the reported version 71.0.3578.98 and unable to reproduce the issue as per comment #5.

1. Launched Chrome and added the test extension provided.
2. Opened Background Devtools page for Test Extension and can see the message 'redirectTest background page loaded'.
3. Opened a new tab and dropped the URL 'http://www.tkqlhce.com/click-5897557-12377205?sid=638468599&afsrc=1&context=loyalty' in the omnibox.
4. Couldn't observe any errors on the Background page.
5. Cleared the console log and navigated to https://www.google.com/aclk?sa=l&ai=DChcSEwjrv9uN-97fAhWOymQKHZJ0ANoYABAAGgJwag&sig=AOD64_1_kEE1pw49PKJax5hEuGK47kyNOg&q=&ved=2ahUKEwj52NWN-97fAhWJ11QKHYBVAggQ0Qx6BAgFEAE&adurl=. Couldn't observe any errors on this page as well.

Attached is the screen cast for reference.

Request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations.

Thanks..
920255.mp4
10.1 MB View Download
Thank you very much for your quick response.
That's curious, as we have been able to reproduce these cases pretty consistently with multiple users on different machines and profiles in different locations.  
We will do some more testing and report back.
Thanks
Project Member

Comment 9 by sheriffbot@chromium.org, Jan 11

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Bisect
casey.c@ Thanks for the update.

As this issue is not reproducible at TE end, removing Needs-Bisect label.
As per comment #8, please add the label back with the exact repro steps, which will be helpful in further triaging.

Thanks.. 
Thanks Susan, 
We are having more people test and finding it inconsistent. We are trying to narrow down why it's intermittent. (It often works in Incognito Mode despite not working in Regular Chrome)
I did notice in your video, you actually did get an error. If you pause the video at exactly 1:12 you can see it, it's not obvious since it's not red.
Thanks for your work on this.


Thank you for your patience.

So we believe the issue works the first time, but not the second time... sometimes if you try too quick it will work the second but not the third.. (I'm not sure about the timing of the caching.) Thus if you clear your cache (Clear Browsing Data) then it works again.

This has allowed me to test and get the exact same call working once and not working once and I have captured it using the Chromium Net Internals Tool.
https://chromium.googlesource.com/chromium/src/+/master/net/docs/crash-course-in-net-internals.md

I have attached two files. You can see the one named 'Second_time' gets the ERR_ABORTED while the first one does not.

Both files are the Single key URL_REQUEST from the log generated by dropping the url http://www.tkqlhce.com/click-5897557-12377205?sid=638468599&afsrc=1&context=loyalty into the address bar.

Thank you.
chrome-net-export-log.zip
6.8 KB Download

Comment 13 by case...@prodege.com, Jan 18 (4 days ago)

Hi, I just wanted to check in.
Have you been able to replicate the Error by going to the url more than once? 

I have verified on multiple machines the ERR_ABORTED doesn't happen on the first navigation to this url
http://www.tkqlhce.com/click-5897557-12377205?sid=638468599&afsrc=1&context=loyalty
But does produce errors on subsequent navigations. However, I re-verified that it never errors on Chrome 68

Sign in to add a comment