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

"Port ps_blend to be a brush shader" regressions #2438

Closed
16 tasks done
Darkspirit opened this issue Feb 17, 2018 · 14 comments
Closed
16 tasks done

"Port ps_blend to be a brush shader" regressions #2438

Darkspirit opened this issue Feb 17, 2018 · 14 comments

Comments

@Darkspirit
Copy link

Darkspirit commented Feb 17, 2018

Regression range: 38df48c...d69bd28 (webrender update)

Edit:
Also affected:

Edit 2:
It seems that only the tab loading animation and whatsapp's file sending menu(?) are fixed by #2443.


Black boxes (Intel Sandybridge Mobile on Linux)

Edit 3:
I can't reproduce them, but the reporter confirmed the same regression range and that they aren't fixed in the try build from #2477.

@kvark
Copy link
Member

kvark commented Feb 23, 2018

I want all the issues to come in like this 😍

@Darkspirit Darkspirit changed the title regression: tab loading animation is broken "Port ps_blend to be a brush shader" regressions Feb 27, 2018
@Darkspirit
Copy link
Author

WR @ b53cf7799a0f5861dfa928ee0ccc66e8d0b78758 try build

mozregression --repo try --launch d115c4c11850c1b1d0b1c847eefc3d959efe0b12 --pref gfx.webrender.all:true

I can reproduce all remaining issues.

@glennw
Copy link
Member

glennw commented Feb 28, 2018

I'll investigate these this week, thanks for the detailed report!

@glennw glennw self-assigned this Feb 28, 2018
@glennw
Copy link
Member

glennw commented Feb 28, 2018

I can repro the akamai bug locally here (even without the theme activated). I'll see if I can narrow that down to a small repro case. Hopefully fixing one of those will get the rest of them, this time.

@glennw
Copy link
Member

glennw commented Feb 28, 2018

This #2477 fixes the akamai test case above. I haven't tested against the other cases yet, but I expect it will probably fix them all. I need to do a try run first to see if it breaks anything else.

@glennw
Copy link
Member

glennw commented Feb 28, 2018

I tested https://vuetifyjs.com/en/components/buttons and http://www.senecacollege.ca/campuses/janelocation.html with this change, and I didn't see any obvious issues.

@Darkspirit
Copy link
Author

Darkspirit commented Feb 28, 2018

mozregression --repo try --launch b6987fdf2f5cad510d74179bb7196829fec1e00e --pref gfx.webrender.all:true

  • vuetifyjs buttons + menu are fixed
  • gmaps looks mostly fine. I saw another issue when Ctrl+Scrolling on it where my whole UI died. (Yesterday I got a crash at this point. Maybe I ran into this, but I don't know.) I will file a seperate bug about that.
  • facebook is fixed
  • akamai is fixed

  • google calendar was possibly the same as the tab loading issue and is fixed. (Fix range)

That webrender update had one more regression: https://bugzilla.mozilla.org/show_bug.cgi?id=1441025
I couldn't reproduce that. (He always had his own special text bugs.) Hopefully that is gone too, but I don't know.
(moved to the next comment)

@Darkspirit
Copy link
Author

Darkspirit commented Mar 1, 2018

Black boxes

I deleted my previous two comments. Things have been confirmed now:

I can't reproduce them, but the reporter confirmed the same regression range and that they aren't fixed in the try build from #2477.

Edit: Some more reports (which I can't reproduce):

@Darkspirit
Copy link
Author

Darkspirit commented Mar 2, 2018

The user who reported these "things are black" regressions still sees issues on already fixed websites:
His screencasts: akamai, gmaps, facebook
His Akamai issue is different from my initial report: Only the outer right part is drawn - in black - on his chrome. Hopefully this makes it easier for you to narrow down the source of this problem.

@Darkspirit
Copy link
Author

Both users affected by black glitches have this graphics card: Mesa DRI Intel(R) Sandybridge Mobile

@glennw
Copy link
Member

glennw commented Mar 6, 2018

My guess is that Sandybridge drivers don't get updated much anymore, if at all. So we'll probably need to get hold of some hardware with that GPU, and find a workaround for what appears to be a driver bug.

@glennw
Copy link
Member

glennw commented Mar 16, 2018

@Darkspirit I think all the remaining issues were related to the Sandybridge GPU only, which is fixed by #2530. Are you fine with closing this one off?

@Darkspirit
Copy link
Author

Awaiting confirmation

@Darkspirit
Copy link
Author

☀️ Verified fixed: All Sandybridge issues are gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants