Closed Bug 1558436 Opened 10 months ago Closed 10 months ago

Runaway memory in, regression


(Core :: Graphics: WebRender, defect, P2)

69 Branch
Windows 10



Tracking Status
firefox-esr60 --- unaffected
firefox67 --- unaffected
firefox68 --- unaffected
firefox69 --- fixed


(Reporter: Mark12547, Assigned: sotaro)


(Regression, )


(4 keywords)


(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

  1. Create a new Nightly profile and use Firefox against the profile to ...
  2. Run
  3. If advertisement page presented, click on X to get to the game.

Actual results:

After playing the game for a short while (maybe up to half of the game), one of these occurs:

  • Tab Crash (usually no dump)
  • Firefox crashes (usually no dump)
  • The complete Windows 10 (64-bit) crashed once (was running mozregression-gui)

Also noticed during game play that the Windows Task Manager shows a steady increase in memory usage with some dips (probably garbage collection) until the tab/Firefox/Windows crashes.

Sample crashes:

Expected results:

Until a few days ago, I could play a number of games at without incident.

mozregression-gui log ends with:

2019-06-11T03:11:15: DEBUG : Found commit message:
Bug 1556340 - Make D3D11TextureData and DXGIYCbCrTextureData alive during host side usage with WebRender r=nical

By Bug 1555544 , it became clear that D3D11TextureData and DXGIYCbCrTextureData should not be deleted before calling RenderDXGITextureHostOGL::EnsureLockable() / RenderDXGITextureHostOGL::EnsureLockable().

With WebRender, the EnsureLockable()s are called on RenderThread asynchronously. Then for achieving the above, it is simpler just to keep D3D11TextureData and DXGIYCbCrTextureData alive during host side usage.

There is already a mechanism to do it. By using NotifyNotUsed, it could be done.

Differential Revision:

2019-06-11T03:11:15: DEBUG : Did not find a branch, checking all integration branches
2019-06-11T03:11:15: INFO : The bisection is done.
2019-06-11T03:11:15: INFO : Stopped

The bisection information shows:

app_name: firefox
build_date: 2019-06-06 02:51:45.923000
build_file: C:\Users\Mark.mozilla\mozregression\persist\
build_type: inbound
changeset: eca88f6069a7859a93bf064f8274a4df919091c0
repo_name: autoland
task_id: Rzh3Td0MRQOpAFARhui10g

about_support_1558436.txt is the about:support for the brand new profile with which I was able to reproduce the tab/firefox crashes.

This is Windows 10 Home (64-bit), version 1903, OS build 18362.145. I also updated the Intel and HP drivers before running the regression.
CPU is Intel i5-7400 (4-core) with Intel HD Graphics 630. 12GB RAM.

Additional observations:

When I turned off "hardware acceleration" the problem went away.

When demonstrating the problem, it doesn't appear to be necessary to actually play the game; without playing (but still on the game screen), Firefox appears to grab 1% of the total memory a bit faster than once a second.

A quick-and-dirty run of the Gecko Profiler, hopefully capturing something useful:

Component: Untriaged → Graphics: WebRender
OS: Unspecified → Windows 10
Product: Firefox → Core
Regressed by: 1556340
Hardware: Unspecified → x86_64
Keywords: crash, reproducible
Ever confirmed: true

Confirming setting to NEW
Win 10 build 1903 May update.

From Computer Management Console-> System
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: firefox.exe (11516) consumed 354996224 bytes, firefox.exe (2272) consumed 178794496 bytes, and firefox.exe (4264) consumed 175439872 bytes.

It seems similar to bug 1558100. D3D11TextureData is created very often in CanvasClient2D::Update(). See bug 1558100 comment 2.

See Also: → 1558100

Sotaro, I will assign this to you for now to verify if the fix for bug 1558100 helps here too

Assignee: nobody → sotaro.ikeda.g
Blocks: wr-69
Priority: -- → P2

(In reply to Jim Jeffery not reading bug-mail 1/2/11 from comment #4)

Win 10 build 1903 May update.

Problem was also happening before the 1903 May update. (I had applied Windows, HP, and Intel software maintenance to current before running mozregression.

Just tested in Nightly Build-id 20190613095633 and this Bug appears to be fixed with the fixing of Bug 1558100.

Confirming, played a whole game - no crashes or abnormal memory use that I could see.

Thanks for the confirmation.

Closed: 10 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1558100
You need to log in before you can comment on or make changes to this bug.