Closed Bug 1647491 Opened 6 years ago Closed 6 years ago

Flickering on the https://www.apple.com/macos/big-sur-preview/ with HD 530 WebRender Win10

Categories

(Core :: Graphics: CanvasWebGL, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla80
Tracking Status
firefox-esr68 --- unaffected
firefox-esr78 --- unaffected
firefox77 --- unaffected
firefox78 --- unaffected
firefox79 + fixed
firefox80 --- fixed

People

(Reporter: jrmuizel, Assigned: jgilbert)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

I get a bunch of flickering on the Notification Center prompt.
In about:support I see a bunch of:

RenderTextureHostOGL: Failed to open shared texture, hr=0x80070057
RenderTextureHostOGL: AcqireSync timeout, hr=0x80070057

I don't see this in Beta

This was probably broken by bug 1632249

Summary: Flickering on the https://www.apple.com/macos/big-sur-preview/ with HD 530 → Flickering on the https://www.apple.com/macos/big-sur-preview/ with HD 530 WebRender Win10
Regressed by: 1632249
Has Regression Range: --- → yes

Yeah, my mozregression session confirms it.

[Tracking Requested - why for this release]: Noticeable regression

Set release status flags based on info from the regressing bug 1632249

Assignee: nobody → jgilbert

I don't see this on Win10+AMD+WR.

Actually I think I do see it.

We might be getting the race condition I was previously worried about, where the content overproduces and so drops the ref on the old-to-it surface before WR gets around to acquiring its own ref to it.

Severity: -- → S2
Priority: -- → P1
Component: Graphics: WebRender → Canvas: WebGL

Yep, it's what I thought:

[client] UseTexture 0x000000004000F5C2 => 0x0000000040010C02
[client] UseTexture 0x0000000040010C02 => 0x00000000C00113C2
[client] UseTexture 0x00000000C00113C2 => 0x00000000400073C2
Exception thrown at 0x00007FF97A0E3E49 in firefox.exe: Microsoft C++ exception: _com_error at memory location 0x000000E24BDFD8D0.
[host] OpenSharedResource(0x00000000C00113C2) failed.

Pushed by jgilbert@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6a693522d3c3 Hold ref to previous webgl frontbuffer while in-flight. r=lsalzman
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80

Please verify!

Flags: needinfo?(jmuizelaar)

Comment on attachment 9160782 [details]
Bug 1647491 - Hold ref to previous webgl frontbuffer while in-flight.

Beta/Release Uplift Approval Request

  • User impact if declined: Black flickering for some WebGL content, including the high-profile URL in in the bug.
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Low risk, as we're just holding on to resources a little longer
  • String changes made/needed: none
Attachment #9160782 - Flags: approval-mozilla-beta?

I don't see the problem anymore.

Flags: needinfo?(jmuizelaar)

Comment on attachment 9160782 [details]
Bug 1647491 - Hold ref to previous webgl frontbuffer while in-flight.

Approved for 79.0b3.

Attachment #9160782 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: