Open
Bug 1706878
Opened 4 years ago
Updated 4 years ago
WebRender initialization failed on Intel Graphics 630
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
NEW
People
(Reporter: yoasif, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
From https://www.reddit.com/r/firefox/comments/mvr7rm/animations_are_choppy_after_the_890b2_update_what/
So I updated Firefox today to version 89.02b. I noticed that everywhere animations are choppy and have some delay to them.
Also, I noticed something weird this morning; RAM usage shoots up to 10GB for Firefox when it's starting up then it goes back to normal afterwards.
Decision Log
HW_COMPOSITING:
available by default
unavailable by runtime: WebRender initialization failed
D3D11_COMPOSITING:
available by default
unavailable by runtime: WebRender initialization failed
DIRECT2D:
available by default
unavailable by runtime: WebRender initialization failed
D3D11_HW_ANGLE:
available by default
GPU_PROCESS:
available by default
failed by runtime: Failed to create remote compositor
WEBRENDER:
available by default
unavailable by runtime: WebRender initialization failed
WEBRENDER_QUALIFIED:
available by default
WEBRENDER_COMPOSITOR:
available by default
WEBRENDER_PARTIAL:
available by default
WEBRENDER_SHADER_CACHE:
available by default
WEBRENDER_OPTIMIZED_SHADERS:
available by default
WEBRENDER_ANGLE:
available by default
WEBRENDER_DCOMP_PRESENT:
available by default
WEBRENDER_SOFTWARE:
available by default
Reporter | ||
Comment 1•4 years ago
|
||
Comment 2•4 years ago
|
||
Attachment 9217628 [details] was flooded by the following log. It is not good. Bug 1706887 is created to suppress the log.
Error: RenderCompositorSWGL failed mapping default framebuffer, no dt
Updated•4 years ago
|
Blocks: gfx-triage
Updated•4 years ago
|
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•