WebRender Compositor returns No Hardware Stretching support
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
People
(Reporter: rdoghi, Assigned: jrmuizel)
References
(Depends on 1 open bug, Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(6 files)
[Affected versions]
Firefox 76.0a1
[Affected platforms]
All
Preconditions:
Have a Laptop with Intel GPU UHD 630 driver versions: 26.20.100.6860
[Steps to reproduce]
- Open the Firefox browser and reach about:support
- Reach the bottom of the Graphics section ie the Decision Log section and verify WEBRENDER_COMPOSITOR
[Expected result]
WEBRENDER_COMPOSITOR shows available by user: Enabled
[Actual result]
WEBRENDER_COMPOSITOR shows unavailable by runtime: No Hardware stretching support
WEBRENDER_QUALIFIED shows denied by env: Not on allowlist.
Please note that in 75.0b2 WebRender_Compositor shows available by user:Enabled
Reporter | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 1•4 years ago
|
||
To address Bug 1618370 , we disable wr native compositor when DirectComposition does not support hardware stretching. It might be mitigated in future.
Reporter | ||
Comment 2•4 years ago
|
||
Shouldnt Intel UHD 630 be supported by Direct Compositor ? is there a list with supported Intel GPU's ?
Comment 3•4 years ago
|
||
It is checked by using IDXGIOutput6::CheckHardwareComposition().
Reporter | ||
Comment 4•4 years ago
|
||
Intel HD 630 and Intel HD 620 GPU's are also affected by this issue.
Assignee | ||
Comment 5•4 years ago
•
|
||
We do get DirectComposition on Kats' Intel HD Graphics 630 with driver 25.20.100.6373 on Win10 1909
Assignee | ||
Comment 6•4 years ago
•
|
||
Also works with Bert's HD Graphics 630 on 26.20.100.7262 combined with a NVidia GTX 1050 Ti on Win10 1809
Assignee | ||
Comment 7•4 years ago
•
|
||
But not on agashlin's HD Graphics 630 combined with a NVIDIA GeForce GTX 1050 on 23.20.16.4973 and Win10 1909
Assignee | ||
Comment 8•4 years ago
|
||
It also works on my HD Graphics 530 on Win 10 1809 on 26.20.100.7263
Comment 9•4 years ago
•
|
||
WebRender native compositor works on Win10 1909 with Intel UHD Graphics 630(26.20.100.7262). 2nd GPU is NVIDIA GeForce GTX 1050 Ti with Max-Q Design(26.21.14.3123).
Reporter | ||
Comment 10•4 years ago
|
||
We have a Desktop PC with Windows 10 1903 with an updated INTEL HD 630 GPU driver to 26.20.100.7263 and it Works in Nightly but in BETA we get the WEBRENDER_COMPOSITOR: blacklisted by runtime: Blacklisted
We also have the following setup:
Dell G3 Laptop with Windows 10 1909, Intel UHD 630 GPU driver v.27.20.100.7988 and an Nvidia GeForce GTX 1050 26.21.14.4219
Nightly - COMPOSITING = WEBRENDER
- WEBRENDER_COMPOSITOR: unavailable by runtime: No hardware stretching support
Beta 75.0b8 - Compositing = Direct 3D 11
- WEBRENDER_QUALIFIED = denied by env: Not on allowlist
- WEBRENDER_COMPOSITOR = unavailable by runtime: No hardware stretching support
Please note that at first we had the Windows 10 1903 with INTEL UHD GPU driver 26.20.100.7262 and we still got the same results, after Windows 10 update to 1909 the driver version changed as well to 27.20.100.7988
I will attach the About:support information from both devices.
Reporter | ||
Comment 11•4 years ago
|
||
Reporter | ||
Comment 12•4 years ago
|
||
Reporter | ||
Comment 13•4 years ago
|
||
Small update on the Dual GPU laptop if I set Nvidia as the main GPU from Nvidia 3D settings im still getting the same No Hardware stretching support for Webrender_compositor
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 14•4 years ago
|
||
It does not work on kvark's HD Graphics 630 with 26.20.100.7261 on Win10 1903
Comment 15•4 years ago
|
||
Updated•4 years ago
|
Comment 16•4 years ago
|
||
Comment 17•4 years ago
|
||
Reporter | ||
Comment 18•4 years ago
|
||
I'm updating the severity of this issue since it blocks our Pre-Release testing.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 19•4 years ago
|
||
Let's wait for the gray line fix before worrying about this again.
Comment 20•4 years ago
|
||
These are current, open bugs with a Severity of critical
. The Severity of these bugs is being changed to S2
to be consistent with the May 4 2020 Severity definitions.
Please let Release Management know if these bugs are still S2
.
Comment 22•2 years ago
|
||
I just wanted to mention that I'm also getting this on my PC, just in case.
https://0bin.net/paste/1G9f-3b6#7th2Kcl15aU0O57yDgZGYUMxSmgQyXiO8j9OWG9iUhg
Updated•3 months ago
|
Description
•