Firefox heap-textures using 4+ GB of memory

UNCONFIRMED
Unassigned

Status

()

Core
Graphics
UNCONFIRMED
4 years ago
3 years ago

People

(Reporter: Wesley Hardman, Unassigned)

Tracking

Trunk
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink:P2])

(Reporter)

Description

4 years ago
Heap textures has grown to 4+ GB.  I don't have that many tabs open (Window1 3 + Window2 2) for a total of 5.  CC/GC didn't help any.  I also closed the only tab that might be heavy on the graphics.  I did have the dev tools open for a while with Log Request and Response Bodies turned on.

Originally posted on mozilla.dev.platform.  Filling bug per Benoit.  I still have Firefox open and it is still around 5 GB total memory usage.

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:30.0) Gecko/20100101 Firefox/30.0

4,783.33 MB (100.0%) -- explicit
├──4,073.86 MB (85.17%) -- gfx
│  ├──4,073.18 MB (85.15%) ── heap-textures
│  └──────0.68 MB (00.01%) ++ (5 tiny)
├────185.48 MB (03.88%) -- js-non-window
│    ├──145.96 MB (03.05%) -- zones
│    │  ├──102.89 MB (02.15%) ++ zone(0x76cb800)
│    │  └───43.07 MB (00.90%) ++ (31 tiny)
│    └───39.52 MB (00.83%) ++ (2 tiny)
├────182.37 MB (03.81%) -- window-objects
│    ├───67.81 MB (01.42%) -- top(none)/detached
│    │   ├──63.47 MB (01.33%) ++ window(chrome://browser/content/browser.xul)
│    │   └───4.34 MB (00.09%) ++ (5 tiny)
│    ├───60.18 MB (01.26%) ++ (10 tiny)
│    └───54.39 MB (01.14%) ++ top([URL], id=1954)
├────134.19 MB (02.81%) -- heap-overhead
│    ├──131.69 MB (02.75%) ── waste
│    └────2.50 MB (00.05%) ++ (2 tiny)
├────114.44 MB (02.39%) ++ (21 tiny)
└─────92.99 MB (01.94%) ── heap-unclassified
.....

        0.22 MB ── canvas-2d-pixels
        0.00 MB ── gfx-d2d-surface-cache
        4.00 MB ── gfx-d2d-surface-vram
      208.90 MB ── gfx-d2d-vram-draw-target
        5.34 MB ── gfx-d2d-vram-source-surface
        1.38 MB ── gfx-surface-win32
        0.00 MB ── gfx-textures
              0 ── ghost-windows
    4,394.14 MB ── heap-allocated
    4,528.33 MB ── heap-committed
          3.05% ── heap-overhead-ratio
              0 ── host-object-urls
        0.00 MB ── imagelib-surface-cache
       24.58 MB ── js-main-runtime-temporary-peak
    5,082.21 MB ── private
    5,221.40 MB ── resident
    6,651.32 MB ── vsize
8,376,692.50 MB ── vsize-max-contiguous
Whiteboard: [MemShrink]
Can you determine steps to reproduce? E.g. opening a particular site? It'll be hard to work out what's wrong without that. Thanks!
(Reporter)

Comment 2

4 years ago
I doubt it.  I'll see what I can do.  Its the first time I have see this happen, and don't recall anything I did unusual.
Is this a 64-bit build? If so where did it come from?
Flags: needinfo?(bugzilla)
(Reporter)

Comment 4

4 years ago
This is 64-bit.  32-bit would have OOM a long time ago.

Built from https://hg.mozilla.org/releases/mozilla-release/rev/10163f891015

VS 2013

I forgot that I also have OMTC enabled.  Probably important.

I have been unable to reproduce it, however I have noticed that heap-textures always increases, and I haven't seen it decrease.  It is currently at 41.37MB.
Flags: needinfo?(bugzilla)
(Reporter)

Comment 5

4 years ago
I think I figured out how to reproduce it. Right now I'm at 456.53 MB

1. Enable OMTC (not sure if this is required).
2. Load a page with an MP4 HTML5 video (1080p videos make it more noticeable).
3. Reload the page and/or load other videos.  (Note: reloading seems to lose effect after a while.)


I tried to reproduce it on Nightly but couldn't get quite the same effect.  On Nightly, heap-textures seems to always stay at 0.  However I did notice:

252.91 MB ── gpu-committed
198.58 MB ── gpu-dedicated

These don't exist on Release.  GC/CC does seem to reduce them somewhat to around 100 MB.
Wesley: I'm a bit confused by comment 5. Can you please clarify which versions you are seeing this problem in? Thanks.
Whiteboard: [MemShrink] → [MemShrink:P2]
You need to log in before you can comment on or make changes to this bug.