Flickering on the https://www.apple.com/macos/big-sur-preview/ with HD 530 WebRender Win10
Categories
(Core :: Graphics: CanvasWebGL, defect, P1)
Tracking
()
| 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)
|
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
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
| Reporter | ||
Updated•6 years ago
|
| Reporter | ||
Comment 1•6 years ago
|
||
I don't see this in Beta
| Reporter | ||
Comment 2•6 years ago
|
||
This was probably broken by bug 1632249
| Reporter | ||
Updated•6 years ago
|
Updated•6 years ago
|
| Reporter | ||
Comment 3•6 years ago
|
||
Yeah, my mozregression session confirms it.
| Reporter | ||
Comment 4•6 years ago
|
||
[Tracking Requested - why for this release]: Noticeable regression
Comment 5•6 years ago
|
||
Set release status flags based on info from the regressing bug 1632249
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 6•6 years ago
|
||
I don't see this on Win10+AMD+WR.
| Assignee | ||
Comment 7•6 years ago
|
||
Actually I think I do see it.
| Assignee | ||
Comment 8•6 years ago
|
||
0x80070057 is E_INVALIDARG: https://james.darpinian.com/decoder/?q=0x80070057
| Assignee | ||
Comment 9•6 years ago
|
||
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.
Updated•6 years ago
|
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 10•6 years ago
|
||
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.
| Assignee | ||
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 15•6 years ago
|
||
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
Comment 17•6 years ago
|
||
Comment on attachment 9160782 [details]
Bug 1647491 - Hold ref to previous webgl frontbuffer while in-flight.
Approved for 79.0b3.
Comment 18•6 years ago
|
||
| bugherder uplift | ||
Description
•