Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XHR requests canceled across a wide range of websites #2901

Closed
Swader opened this issue Jan 10, 2019 · 25 comments · Fixed by brave/brave-core#1361
Closed

XHR requests canceled across a wide range of websites #2901

Swader opened this issue Jan 10, 2019 · 25 comments · Fixed by brave/brave-core#1361

Comments

@Swader
Copy link

Swader commented Jan 10, 2019

Full discussion in Twitter here: https://twitter.com/bitfalls/status/1082896409299505152


Version 0.59.20 Chromium: 72.0.3626.28 (Official Build) beta (64-bit)
Win10 x64.

  • Does not happen on OS X.
  • Does not happen in private browsing mode.
  • All extensions were OFF for the duration of reproducing the problems (I have only 3 extensions total - metamask, json viewer and Workona).
  • Shields are completely off during all these tests.

On certain websites, ajax requests get canceled for no apparent reason (code -3, ERR_ABORT).

Examples are: https://www.diffbot.com/careers and https://gitcoin.co/explorer?network=mainnet&keywords=nimbus&order_by=-web3_created

Here is a HAR reproduction for Diffbot: https://gist.github.com/Swader/a994365480ee63927eb4045163133f89

Example screenshot:

capture

@srirambv
Copy link
Contributor

srirambv commented Jan 11, 2019

This looks fixed on the new beta. Could have been the CORS issue which wasn't fixed in 0.59.20.
screenshot from 2019-01-11 09-19-58

@Swader mind checking it on the new beta that went out yesterday?

@srirambv srirambv added the needs-more-info The report requires more detail before we can decide what to do with this issue. label Jan 11, 2019
@Swader
Copy link
Author

Swader commented Jan 11, 2019

Still happens, same conditions. All extensions and shields off. I recommend adding a debug output and a command line --debug flag to the executable before every ERR_ABORT emit so that we can find out when these canels are being triggered.

capture
capture2

@srirambv
Copy link
Contributor

Just to confirm you are still seeing this on 0.59.21 right?

@Swader
Copy link
Author

Swader commented Jan 11, 2019

Correct: Version 0.59.21 Chromium: 72.0.3626.28 (Official Build) beta (64-bit)

@srirambv
Copy link
Contributor

srirambv commented Jan 11, 2019

@btlechowski @GeetaSarvadnya could you guys give it a try on Windows?

cc: @iefremov @simonhong

@srirambv srirambv added the needs-investigation A bug not 100% confirmed/fixed label Jan 11, 2019
@srirambv srirambv added this to the 1.x Backlog milestone Jan 11, 2019
@iefremov
Copy link
Contributor

I don't think its the CORS issue, looks like smth different.
Maybe check this behavior in Chrome?

@srirambv
Copy link
Contributor

I can't reproduce the issue on Linux with the same build.

@Swader
Copy link
Author

Swader commented Jan 11, 2019

It works in latest Chrome and Opera.
It does not happen on any other OS, or even in private mode on Win+Brave.

@iefremov
Copy link
Contributor

Thanks for checking this. Probably it is also worth checking in Chrome version corresponding to the problematic Brave build (Chromium: 72.0.3626.28) @srirambv

@Swader
Copy link
Author

Swader commented Jan 11, 2019

Another example: https://prvikvadrat.hr/

@Swader
Copy link
Author

Swader commented Jan 14, 2019

Another example on Github. A few refreshes with cache off helped.

696bf552-c224-495d-9658-637a64c4cdce png

@cndouglas
Copy link
Contributor

cndouglas commented Jan 14, 2019

+1 from me (#2930).

  • Happens on the current beta (0.59.x) and dev (0.60.x) releases, but not the current public release (0.58.x).
  • Happens on macOS (10.14)
  • Seems to happen with a fresh profile after restarting the browser at least once
  • Turning off shields does not help
  • More examples of websites:

@bbondy bbondy added the priority/P1 A very extremely bad problem. We might push a hotfix for it. label Jan 15, 2019
@bbondy bbondy modified the milestones: 1.x Backlog, 0.59.x - Beta Jan 15, 2019
@bbondy
Copy link
Member

bbondy commented Jan 15, 2019

this seems serious and new based on ^, putting P1 and putting as release/blocking.

@iefremov iefremov self-assigned this Jan 15, 2019
@bsclifton
Copy link
Member

bsclifton commented Jan 15, 2019

@liunkae can you please update to latest? I'm curious if recent fixes resolve this problem for you (works for me!™)

For what it's worth, I'm on DEV channel (0.60.12)

@iefremov
Copy link
Contributor

Can't reproduce on Dev/Beta on MacOS.

Anyone with a stable repro, please save a netlog. To do this:

  1. Open brave://net-export/
  2. Click "Start logging to disk"
  3. Reproduce the bug in some other tab
  4. Return to brave://net-export, click "Stop logging", attach the resulted file to this ticket :)

Thanks

@Swader
Copy link
Author

Swader commented Jan 15, 2019

Here's an older export from me.
chrome-net-export-log.zip

@cndouglas
Copy link
Contributor

Here's a netlog: chrome-net-export-log.json.zip

Still reproduces (100% of the time) for me with the following:

Brave | 0.60.13 Chromium: 72.0.3626.53 (Official Build) dev(64-bit)
Revision | 98434e6cd182d68ce396daa92e9c6310422e6763-refs/branch-heads/3626@{#620}
OS | Mac OS X
macOS version 10.14.2

Steps to reproduce:

  1. Start with a fresh profile.
  2. Quit the browser.
  3. Start Brave again.
  4. Go to https://brave.com/jobs
  5. Notice that the job listings do not load, even with shields off:

The developer console shows that one of the resources was canceled:

@bbondy
Copy link
Member

bbondy commented Jan 15, 2019

We tracked it down to some code for the DOM distiller. Working on a fix.

@kjozwiak
Copy link
Member

Removed OS/Windows as this is affecting macOS as well.

@srirambv
Copy link
Contributor

srirambv commented Jan 18, 2019

Verification passed on

Brave 0.59.25 Chromium: 72.0.3626.53 (Official Build) beta(64-bit)
Revision 98434e6cd182d68ce396daa92e9c6310422e6763-refs/branch-heads/3626@{#620}
OS Linux

Verification passed on

Brave 0.59.25 Chromium: 72.0.3626.53 (Official Build) beta (64-bit)
Revision 98434e6cd182d68ce396daa92e9c6310422e6763-refs/branch-heads/3626@{#620}
OS Windows 10

Verification PASSED on macOS 10.14.2 x64 using the following build:

Brave 0.59.28 Chromium: 72.0.3626.64 (Official Build) beta(64-bit)
Revision eaa9668e80ce5405e7f1902579558ea725c06ca1-refs/branch-heads/3626@{#708}
OS Mac OS X

@Swader
Copy link
Author

Swader commented Jan 18, 2019

Please update issue to ping us when this lands in beta on Win

@bbondy
Copy link
Member

bbondy commented Jan 18, 2019

It's already updated on dev and beta

@Swader
Copy link
Author

Swader commented Jan 18, 2019

Indeed it seems to work now. Can you explain how, without an update process?

@srirambv
Copy link
Contributor

@Swader your app should have been updated to 0.59.25. Could you check brave://version?

@Swader
Copy link
Author

Swader commented Jan 20, 2019

It did indeed, but I don't remember the update process having happened. Might have occurred between a PC restart. Anyway thanks looks good now!

@kjozwiak kjozwiak added QA/Yes QA Pass-macOS release-notes/exclude and removed needs-more-info The report requires more detail before we can decide what to do with this issue. needs-investigation A bug not 100% confirmed/fixed labels Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants