Tab loading icon remains in the tab after page finishes loading

[chrisB28]

Description

Occasionally the loading icon will stay in the tab header, often in the wrong place.

Steps to Reproduce

Most often happens when multiple tabs are open, loading icon remains in the tab. Positioning varies, sometimes overlays the page's icon or appears over the text.

Screenshot:

Reproduces how often:

Intermittent

Brave version

Brave	0.70.123 Chromium: 78.0.3904.97 (Official Build) (64-bit)
Revision	021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859}
OS	Windows 10 OS Version 1803 (Build 17134.1069)
JavaScript	V8 7.8.279.23
Flash	(Disabled)
User Agent	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36

Other Additional Information:

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

[bsclifton]

@chrisB28 can you update to our newest version (1.0.0)? I'm curious if this still happens

Please let us know! If it does, would you mind sharing the status of items under Graphics Feature Status on brave://gpu? Thanks! 😄

[chrisB28]

I've updated and will test over the next few days to see if this still occurs, thanks.

Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Hardware accelerated
Hardware Protected Video Decode: Hardware accelerated
Rasterization: Hardware accelerated
Skia Renderer: Disabled
Video Decode: Hardware accelerated
Viz Display Compositor: Enabled
Viz Hit-test Surface Layer: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated

Brave	1.0.0 Chromium: 78.0.3904.97 (Official Build) (64-bit)
Revision	021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859}

[chrisB28]

Still happening!

[bsclifton]

+1 from @StephD via #7006

[rebron]

cc: @petemill @simonhong Any ideas on this one?