1383449 - Sometimes loading spinner animation has blue background after opening many tabs in one go

Status: VERIFIED DUPLICATE of bug 1379052

(Core :: Graphics: Layers, defect, P3)

Description

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

Attachment: Screencast.mp4

STR:
1. Open about 50 bookmarks in one go
and see that on some tabs loading spinner is animated in odd way

Regression:
I'm pretty sure, that regressed in today build (2017-07-22), but didn't see anything suspicious in landing patches from Theme/Toolbars and Customization components. I will need to diagnose it deeper.

Comment 1

[Marcia Knous [:marcia]]

Triage team requested that someone from QE try to reproduce this. Adding a ni on Andrei.

Comment 2

[Emil Ghitta, QA [:emilghitta]]

Attachment: Issue.png

Hi Virtual_MAN!

Here are some notes:
-I managed to reproduce this issue only twice and didn't managed to find proper steps to reproduce this much easier.

-It seems that I could reproduce this issue by opening the "Media Player Classic" link (from the https://forum.doom9.org/showthread.php?t=166689 website) while having previously made ~ 40 bookmarks.

-I think that the loading spinner animation has a different behavior if the "Cannot contact reCAPTCHA. Check your connection and try again" message is displayed in a opened background tab (I didn't managed to reproduce this on other tabs that didn't displayed any error). I also tried to investigate if this issue is caused by that error, but I didn't find the exact steps on how to get that error message much more often.

Any thoughts on this? 

Thanks!

Comment 3

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

I suspect that it could be caused by bug #1356317.
I'm ni'ing more knowledge persons in that area.

Comment 4

[Kris Maglione [:kmag]]

Bug 1356317 does not seem like a likely candidate. That only affects the painting of popups, and no popups are involved here.

If you can find a regression range, that would help. It seems likely that this has something to do with opening modal alerts in background tabs that are still loading. But it may also be related to changes to the implementation to allow it to be animated entirely on the compositor thread.

Comment 5

[Peter Chang[:pchang]]

I agree that bug 1356317 only affected the popups but this bug was not related to popups.

Comment 6

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

OK. Thanks for replys, so real hunt for regression begins.

Comment 7

[Milan Sreckovic [:milan] (needinfo for best results)]

Is this still a problem?  Any luck with the regression range?

Comment 8

[Milan Sreckovic [:milan] (needinfo for best results)]

Mike, we had these never ending spinners on tabs before, no?

Comment 9

[Mike Conley (:mconley) (:⚙️)]

(In reply to Milan Sreckovic [:milan] from comment #8)
> Mike, we had these never ending spinners on tabs before, no?

I was getting something similar to this in bug 1385348, and I had pinned it on being in an RCWN experiment cohort.

Hey Virtual_ManPL - if you go to about:networking and bypass the warning, and choose "RCWN Status" in the bottom left, is the RCWN Status in that pane set to true?

Comment 10

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

(In reply to Milan Sreckovic [:milan] from comment #7)
> Is this still a problem? Any luck with the regression range?

I can't reproduce it anymore for now, but I will leave bug open for a few days to test it deeply.


(In reply to Mike Conley (:mconley) - Holiday until August 8th from comment #9)
> Hey Virtual_ManPL - if you go to about:networking and bypass the warning,
> and choose "RCWN Status" in the bottom left, is the RCWN Status in that pane
> set to true?

Hi, OK. I will do that. Thank you very much for information.

Comment 11

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

I can't reproduce it anymore, starting from Mozilla Firefox Nightly 57.0a1 (2017-08-07), so I suspect that patch from bug #1379052, also fixed this similar issue.