Brave-browser: brave stalling/beach balling when auto-completing URLs via tab

[kjozwiak]

Description

Sometimes when you quickly click on the URL bar and try auto-completing a URL via the TAB, the cursor will start beach balling and Brave will stall for a few seconds until the URL is completed.

I've ran into this a few times recently and it happens at least ~3-4 times a day.

Steps to Reproduce

I don't really have STR but it usually happens when Brave has been idling for a bit of time and you quickly click on the URL bar, start typing something and press TAB to auto-complete.

Actual result:

Brave stalls and starts beach balling for a few seconds until the URL auto-completes.

Expected result:

Brave shouldn't be stalling nor beach balling when auto-completing URLs.

Reproduces how often:

As mentioned above, it happens a few times a day but it's not easy to reproduce as it doesn't always happen. I seem to reproduce when I try auto-completing a URL after Brave has been idle for ~20min.

Brave version (brave://version info)

Brave | 1.5.22 Chromium: 79.0.3945.117 (Official Build) nightly (64-bit)
-- | --
Revision | 04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019}
OS | macOS Version 10.15.2 (Build 19C57)

Version/Channel Information:

• Can you reproduce this issue with the current release? Yes, reproduced
• Can you reproduce this issue with the beta channel? Not 100% sure
• Can you reproduce this issue with the dev channel? Not 100% sure
• Can you reproduce this issue with the nightly channel? Yes, reproduced

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields? N/A
• Does the issue resolve itself when disabling Brave Rewards? N/A
• Is the issue reproducible on the latest version of Chrome? N/A

Miscellaneous Information:

CCing @brave/legacy_qa @rebron @bsclifton @snyderp

[pes10k]

I am also seeing this as recent as "Version 1.4.56 Chromium: 79.0.3945.117 (Official Build) dev (64-bit)".

Pretty frustrating, maybe locks brave up for ~5 sec

[bsclifton]

@snyderp are you running on macOS also?

[pes10k]

@bsclifton yep!

[bsclifton]

@snyderp is this still happening w/ latest version of Nightly? We recently disabled out of process rasterization because of reports that it was crashing / causing artifacts / causing hangs for some users

Guessing it's something else, but wanted to check first 😄

[pes10k]

I have not seen it in the last two nightlies. I will report back here if I notice it again.

In general through, i see (saw?) it on tab autocomplete / omnibar issues most, but occasionally on same page, across-origin navigations, which might point to some per-process site-isolation issue

[rebron]

Possibly related to https://github.com/brave/brave-browser/issues/7199.

[pes10k]

Most def related, I bet a dupe

On Jan 14, 2020, at 11:37, Rafael Ebron [e-mail] wrote:


Possibly related to #7199.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[pes10k]

Just experienced again with Version 1.4.58 Chromium: 79.0.3945.117 (Official Build) dev (64-bit)

[bsclifton]

@snyderp does it repro if you disable rewards? If not, I think we can de-dupe this issue to https://github.com/brave/brave-browser/issues/7199

[bmatzner]

Seeing the same result on Catalina 10.15.2 (19C57) with Version 1.2.42 Chromium: 79.0.3945.117 (Official Build) (64-bit) with rewards enabled. Effect occurs after the browser has been idle for some time. Beach ball upon clicking in the omnibar and attempting to type. Entered text will appear after a few seconds. Will continue to test with rewards disabled.

[kjozwiak]

@bsclifton @rebron I disabled Rewards as mentioned on Friday during our triage meeting and I managed to reproduce the issue with the same profile while Rewards was disabled. I'm not 100%, but I don't think it's related to Rewards.

@bmatzner if you disable rewards via brave://rewards, can you still manage to reproduce the issue?

[bmatzner]

@kjozwiak Have been using Brave with Rewards disabled for a few days, and I'm afraid the issue is still there. After a while, in a new tab, when entering text, the beach ball appears.

[bsclifton]

@bmatzner thanks for confirming that it does not solve the problem 👍 We'll need to continue investigating

[rebron]

@bmatzner Can we have you try one more time with 1.5.115 Chromium: 80.0.3987.149.
May have been resolved with the most recent Chromium versions.

@pes10k Any more beachballing with url/autocomplete?

[pes10k]

@rebron i haven't seen this in a while 👍

[bmatzner]

Same here, haven‘t seen the behavior in a couple of days. Thanks so much!

[kjozwiak]

Haven't seen this in a long time either. Must have been resolved in one of the Chromium bumps 👍