Closed Bug 1566875 Opened 5 years ago Closed 5 years ago

Ship WebRender on Laptop Nvidia with small screen (<= 1920x1200)

Categories

(Core :: Graphics: WebRender, task, P2)

72 Branch
Unspecified
Windows 10
task

Tracking

()

VERIFIED FIXED
mozilla72
Tracking Status
firefox70 --- disabled
firefox71 --- disabled
firefox72 + disabled
firefox73 --- verified

People

(Reporter: jbonisteel, Assigned: aosmond)

References

Details

Attachments

(1 file)

We'd like to ship WebRender on Nvidia Laptops with small screens (<= 1920x1200) with 71

Tracking for 71 as the target release.

Changing the priority to p2 as the bug is tracked by a release manager for the current nightly.
See What Do You Triage for more information

Priority: P3 → P2
Version: 70 Branch → 71 Branch
Assignee: nobody → aosmond
Status: NEW → ASSIGNED
Depends on: 1596460

This is getting bumped to 72. Because of the following lines:

https://searchfox.org/mozilla-beta/rev/8330ececd4e18c759ce4bf99fac0813d22b1cd09/gfx/thebes/gfxPlatform.cpp#2935
https://searchfox.org/mozilla-beta/rev/8330ececd4e18c759ce4bf99fac0813d22b1cd09/gfx/thebes/gfxPlatform.cpp#3007

We never actually enabled this on 71 beta in the first place. As such, it is probably best to defer to 72.

Version: 71 Branch → 72 Branch
Pushed by aosmond@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4279ebeb54cd Allow WebRender to be qualified on Windows/NVIDIA/laptop/small screens. r=jrmuizel
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
Blocks: wr-72

We're going to back this out of beta to minimize risk.

We have decided to not ship this target for 72. We are monitoring some UI glitches we are seeing reports of and want to avoid shipping WebRender further until we have a better understanding of what is causing those bugs. Metabug for tracking those glitches: https://bugzilla.mozilla.org/show_bug.cgi?id=1604492

Does that mean we need to land a patch in tree or is that remotely controlled?

(In reply to Julien Cristau [:jcristau] from comment #9)

Does that mean we need to land a patch in tree or is that remotely controlled?

Jeff or Jessie can you confirm whether this requires a respin of the release candidate build vs a normandy pref rollout?

Flags: needinfo?(jmuizelaar)
Flags: needinfo?(jbonisteel)

This will require a respin.

Flags: needinfo?(jmuizelaar)
Flags: needinfo?(jbonisteel)

I was considering making a more targeted patch to do this but the safest thing might be to just back out https://hg.mozilla.org/mozilla-central/rev/4279ebeb54cd on the release branch. Julien can you cause this?

Flags: needinfo?(jcristau)

This issue is verified as fixed in our latest Nightly build 73.0a1 (2020-01-03).

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: