1334604 - GPU process has high CPU and RAM usage if a specific page is in background

Status: UNCONFIRMED

(Core :: Graphics, defect, P3)

Description

[Fanolian]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170127030206

Steps to reproduce:

1. (New profile optional) Open https://thenextweb.com/hard-core-high-tech/2017/01/27/porn-sites-are-safer-than-you-think/ in a tab. (The page is safe for work)
2. Open a new tab. Stay in this tab and wait for about 20 seconds.
3. Observe GPU process' CPU and memory usage. (I use Task Manager)


Actual results:

CPU usage climbs to >14% (on my 4c8t CPU). RAM usage (not GPU ram) climbs to >300MB from about 100MB. The values are taken from Windows' Task Manager.

If I switch back to thenextweb tab, CPU usage drops to about 2.5% which is already higher than usual. RAM usage drops to about 100MB which is about 60MB higher than before opening the tab.

Closing the affected tab will bring CPU and memory usage back to normal.

Comment 1

[Fanolian]

Attachment: The offending page

Here's a backup of the offending page.

Comment 2

[Fanolian]

Attachment: A zip of the offending page

Here's a backup of the offending page.

Comment 3

[Fanolian]

The Graphics section in about:support
Note:
1. GPU#2 (Intel GPU) is not actively using.
2. Nvidia driver version is 378.49 (latest)

Graphics
Features
Compositing	Direct3D 11
Asynchronous Pan/Zoom	wheel input enabled; touch input enabled; scrollbar drag enabled
WebGL Renderer	Google Inc. -- ANGLE (NVIDIA GeForce GTX 760 Direct3D11 vs_5_0 ps_5_0)
WebGL2 Renderer	Google Inc. -- ANGLE (NVIDIA GeForce GTX 760 Direct3D11 vs_5_0 ps_5_0)
Audio Backend	wasapi
Direct2D	true
DirectWrite	true (10.0.14393.351)

GPU #1
Active	Yes
Description	NVIDIA GeForce GTX 760
Vendor ID	0x10de
Device ID	0x1187
Driver Version	21.21.13.7849
Driver Date	1-20-2017
Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dumx,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dum,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um
Subsys ID	282b1462
RAM	4096

GPU #2
Active	No
Description	Intel(R) HD Graphics 4600
Vendor ID	0x8086
Device ID	0x0412
Driver Version	20.19.15.4531
Driver Date	9-29-2016
Drivers	igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32
Subsys ID	0000000c
RAM	Unknown

Diagnostics
ClearType Parameters	DISPLAY1 [ Gamma: 2.2 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ] DISPLAY2 [ Gamma: 2.4 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ]
AzureCanvasAccelerated	0
AzureCanvasBackend	Direct2D 1.1
AzureCanvasBackend (UI Process)	skia
AzureContentBackend	Direct2D 1.1
AzureContentBackend (UI Process)	skia
AzureFallbackCanvasBackend (UI Process)	cairo
GPUProcessPid	1944
GPUProcess	
ClearType Parameters	DISPLAY1 [ Gamma: 2.2 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ] DISPLAY2 [ Gamma: 2.4 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ]

Decision Log
D3D9_COMPOSITING	
disabled by default: Disabled by default

Comment 4

[Sotaro Ikeda [:sotaro]]

ClientLayerManager::ClearCachedResources() might not be called on correct timing.

Comment 5

[David Anderson [:dvander] - inactive, e-mail if emergency]

GPU process memory looks fairly steady on my system, ~50MB. If you try Firefox 54 beta, about:memory should give you a GPU process snapshot, and that might reveal more information?

Comment 6

[Fanolian]

(In reply to David Anderson [:dvander] from comment #5)
> GPU process memory looks fairly steady on my system, ~50MB. If you try
> Firefox 54 beta, about:memory should give you a GPU process snapshot, and
> that might reveal more information?

The site may have changed and I can no longer reproduce the high CPU and RAM usage by visiting the link in comment 0.
However I can still reproduce the issue on Nightly 2017-04-21 build with the attached backup of the offending site (comment 2).

Comment 7

[David Anderson [:dvander] - inactive, e-mail if emergency]

The snapshot looks pretty steady on my system as well. An about:memory dump could help a lot. It'd also be worth checking if you see similar content process memory usage when the gpu process is disabled (about:config, layers.gpu-process.enabled = false)

Comment 8

[Fanolian]

Attachment: memory-report_thenextweb.json.gz

about:memory dump in a new profile with only about:memory and the offending page loaded, during high CPU/RAM usage from GPU process.

The relevant bits about GPU process is attached below. It is odd because about:memory does not agree with the reading on Windows 10 Task Manager.

GPU (pid 7912)
Explicit Allocations

2.10 MB (100.0%) -- explicit
├──1.03 MB (49.00%) -- heap-overhead
│  ├──0.53 MB (25.16%) ── bin-unused
│  ├──0.47 MB (22.49%) ── page-cache
│  └──0.03 MB (01.35%) ── bookkeeping
├──0.69 MB (32.64%) ── heap-unclassified
├──0.17 MB (07.93%) ── profiler/profiler-state
├──0.10 MB (04.58%) -- xpcom
│  ├──0.09 MB (04.15%) ── component-manager
│  └──0.01 MB (00.43%) ── category-manager
├──0.06 MB (02.98%) -- atom-tables
│  ├──0.06 MB (02.98%) ── main
│  └──0.00 MB (00.00%) ── static
└──0.06 MB (02.88%) ── telemetry

Other Measurements

4,095.94 MB (100.0%) -- address-space
├──3,697.63 MB (90.28%) ── free(segments=131)
├────304.73 MB (07.44%) -- commit
│    ├──139.42 MB (03.40%) -- image
│    │  ├───85.84 MB (02.10%) ── execute-read(segments=88)
│    │  ├───46.21 MB (01.13%) ── readonly(segments=190)
│    │  └────7.37 MB (00.18%) ++ (2 tiny)
│    ├──118.33 MB (02.89%) -- private
│    │  ├───80.51 MB (01.97%) ── readwrite+writecombine(segments=480)
│    │  └───37.82 MB (00.92%) ++ (6 tiny)
│    └───46.98 MB (01.15%) ++ mapped
└─────93.58 MB (02.28%) -- reserved
      ├──71.04 MB (01.73%) ── private(segments=565)
      └──22.54 MB (00.55%) ++ (2 tiny)

2.10 MB (100.0%) -- heap-committed
├──1.07 MB (51.00%) ── allocated
└──1.03 MB (49.00%) ── overhead

9 (100.0%) -- observer-service
└──9 (100.0%) -- referent
   ├──9 (100.0%) ── strong
   └──0 (00.00%) ++ weak

    1.07 MB ── heap-allocated
    1.00 MB ── heap-chunksize
    4.00 MB ── heap-mapped
  127.47 MB ── private
  154.86 MB ── resident
  113.98 MB ── resident-unique
    9.64 MB ── system-heap-allocated
  398.24 MB ── vsize
1,805.94 MB ── vsize-max-contiguous

End of GPU (pid 7912)

Comment 9

[Fanolian]

Attachment: GPU_thenextweb.PNG

Windows 10 Task Manager is reporting high CPU/RAM usage on GPU process, while about:memory is not showing it.

Comment 10

[Fanolian]

Attachment: GPUoff_thenextweb.PNG

When GPU Process is disabled, Web Content Process CPU usage is skyrocketed to 55%-85% while RAM usage stays relatively normal.

If e10s is disabled altogether, no high CPU/RAM usage is observed.