Significantly higher GPU use in Firefox on bilibili.com when compared to Chromium browsers
Categories
(Core :: Graphics: Canvas2D, defect, P3)
Tracking
()
People
(Reporter: esmyth, Unassigned)
References
(Blocks 1 open bug)
Details
Basic information
Steps to Reproduce:
- Navigate to https://www.bilibili.com/video/BV1G54y1D766?spm_id_from=333.851.b_7265706f7274466972737431.7
- Play video
Expected Results:
2-3% CPU, 15-16% GPU utilization (Edge, Chrome)
Actual Results:
17-20% CPU, 55-65% GPU utilization - System 1
7-10% CPU, 0% GPU utilization across 2 processes (17-20% total) - System 2
More information
SUMO user report: https://support.mozilla.org/en-US/questions/1297477
Profile URL:
- System 1: https://share.firefox.dev/3k7tXg0
- System 2: https://share.firefox.dev/2PmPLGg
System 1 configuration:
OS version: Windows 10 Pro build 18363
GPU model: NVIDIA GeForce GTX 1050 Ti
Number of cores: 4
Amount of memory (RAM): 16GB
System 2 configuration:
OS version: Windows 10 Pro build 19041
GPU model: Intel UHD Graphics 630/NVIDIA GeForce GTX 1050 Ti w/ Max-Q
Number of cores: 6
Amount of memory (RAM): 32GB
Comment 1•5 years ago
|
||
This profile looks like we're just spending time waiting for the rendering thread to read the canvas data. I don't know our current architecture well but my guess is that just means we're pretty busy rendering? Judging the high GPU that doesn't seem unfeasible. This feels like a graphics issue to me. Any ideas Jeff? Ideally the profile would include the thread doing the rendering of the canvas content, but I don't know which thread that is these days :).
Updated•5 years ago
|
Comment 2•5 years ago
|
||
I see canvas perf being a problem here too.
Updated•5 years ago
|
Description
•