Memory usage increasing on a http://www.theage.com.au page

RESOLVED INVALID

Status

()

Firefox
Untriaged
RESOLVED INVALID
6 years ago
5 years ago

People

(Reporter: Simon Burge, Unassigned)

Tracking

15 Branch
x86
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [Memshrink:P3], URL)

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20100101 Firefox/15.0
Build ID: 20120824154833

Steps to reproduce:

Open http://www.theage.com.au/it-pro/security-it/is-cloud-computing-secure-20120725-22pti.html on a Windows 7 32-bit desktop with 4GB of RAM.  Noscript is installed, with theage.com.au, twimg.com, google.com and twitter.com enabled, all other domains on this page blocked.


Actual results:

The "about:memory" page reports gradually increasing usage for the window-objects for the page (6.13MB at 11:30am, 26.41MB at 1:45pm) with both the layout/arenas area and the dom area growing.  The compartment for the page seems to vary between 5MB and 13MB so far, currently at 6.2MB.

In previous sessions, firefox has grown to approx 1.8GB virtual size then crashes.

This problem has existed for a while (months).  I updated to Firefox 15 today and the problem still exists.


Expected results:

Expected memory usage to remain constant.

Updated

6 years ago
Whiteboard: [Memshrink]

Comment 1

6 years ago
On Mozilla/5.0 (Windows NT 6.1; rv:18.0) Gecko/18.0 Firefox/18.0 (20120829030520) it went up to 8.91 MB for window-objects.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I can reproduce this.  I kept just that page and about:memory open for about 5
hours.  Relevant parts of the two about:memory snapshots are at the bottom of
this comment.

Comparing the start measurements to the end measurements, explicit
jumped by 107MB, from 116MB to 223MB.  This was entirely due to two things:

- The theage.com.au window jumped by 96MB, from 19MB to 115MB.
- heap-unclassified jumped by 13MB, from 23MB to 36MB.

Within the theage.com.au window the changes were all "layout" and "dom";  "js"
and "style-sheets" were unchanged.  Judging from the "dom" numbers, DOM nodes
are being added continuously.  There's some dynamic stuff on the page (e.g.
ads, a twitter feed) that could be responsible, but the various
Twitter/doubleclick/Facebook/Google+ windows don't show increasing memory
consumption, so maybe not.

I guess the next thing to try is to see if this happens in a different browser.


START
-----
115,961,112 B (100.0%) -- explicit
├───43,427,184 B (37.45%) -- window-objects
│   ├──32,572,784 B (28.09%) -- top(http://www.theage.com.au/it-pro/security-it/is-cloud-computing-secure-20120725-22pti.html, id=14)
│   │  ├──31,738,416 B (27.37%) -- active
│   │  │  ├──19,410,216 B (16.74%) -- window(http://www.theage.com.au/it-pro/security-it/is-cloud-computing-secure-20120725-22pti.html)
│   │  │  │  ├──13,044,184 B (11.25%) -- js
│   │  │  │  │  ├──11,627,688 B (10.03%) -- compartment(http://www.theage.com.au/it-pro/security-it/is-cloud-computing-secure-20120725-22pti.html)
...
│   │  │  │  │  └───1,416,496 B (01.22%) -- compartment(http://www.theage.com.au/it-pro/security-it/is-cloud-computing-secure-20120725-22pti.html, about:blank)
...
│   │  │  │  ├───2,954,224 B (02.55%) -- layout
│   │  │  │  │   ├──1,363,104 B (01.18%) ── style-sets [5]
│   │  │  │  │   ├────740,144 B (00.64%) ── pres-shell [5]
│   │  │  │  │   ├────326,768 B (00.28%) -- frames
│   │  │  │  │   │    ├───84,784 B (00.07%) ── nsTextFrame
│   │  │  │  │   │    ├───82,384 B (00.07%) ── nsBlockFrame
│   │  │  │  │   │    ├───41,160 B (00.04%) ── nsInlineFrame
│   │  │  │  │   │    ├───40,592 B (00.04%) ── nsHTMLScrollFrame
│   │  │  │  │   │    ├───31,944 B (00.03%) ── sundries [5]
│   │  │  │  │   │    ├───16,800 B (00.01%) ── nsContinuingTextFrame
│   │  │  │  │   │    ├───15,664 B (00.01%) ── nsPlaceholderFrame
│   │  │  │  │   │    └───13,440 B (00.01%) ── nsBulletFrame
│   │  │  │  │   ├────200,960 B (00.17%) ── style-contexts [5]
│   │  │  │  │   ├────150,624 B (00.13%) ── rule-nodes [5]
│   │  │  │  │   ├─────62,592 B (00.05%) ── line-boxes [5]
│   │  │  │  │   ├─────57,696 B (00.05%) ── text-runs [5]
│   │  │  │  │   └─────52,336 B (00.05%) ── pres-contexts [5]
│   │  │  │  ├───2,598,416 B (02.24%) ── style-sheets [4]
│   │  │  │  └─────813,392 B (00.70%) -- dom
│   │  │  │        ├──465,888 B (00.40%) ── element-nodes [5]
│   │  │  │        ├──265,648 B (00.23%) ── text-nodes [5]
│   │  │  │        ├───54,272 B (00.05%) ── other [12]
│   │  │  │        ├───16,544 B (00.01%) ── orphan-nodes
│   │  │  │        └───11,040 B (00.01%) ── comment-nodes [3]
...
├───22,842,213 B (19.70%) ── heap-unclassified


AFTER 5 HOURS
-------------
222,882,968 B (100.0%) -- explicit
├──136,191,280 B (61.10%) -- window-objects
│  ├──123,924,072 B (55.60%) -- top(http://www.theage.com.au/it-pro/security-it/is-cloud-computing-secure-20120725-22pti.html, id=14)
│  │  ├──123,418,608 B (55.37%) -- active
│  │  │  ├──114,865,072 B (51.54%) -- window(http://www.theage.com.au/it-pro/security-it/is-cloud-computing-secure-20120725-22pti.html)
│  │  │  │  ├───55,219,024 B (24.77%) -- layout
│  │  │  │  │   ├──17,555,144 B (07.88%) -- frames
│  │  │  │  │   │  ├───4,837,840 B (02.17%) ── nsTextFrame
│  │  │  │  │   │  ├───3,845,144 B (01.73%) ── nsBlockFrame
│  │  │  │  │   │  ├───3,689,400 B (01.66%) ── nsHTMLScrollFrame
│  │  │  │  │   │  ├───3,393,240 B (01.52%) ── nsInlineFrame
│  │  │  │  │   │  ├─────823,440 B (00.37%) ── nsContinuingTextFrame
│  │  │  │  │   │  ├─────596,400 B (00.27%) ── nsImageFrame
│  │  │  │  │   │  ├─────326,480 B (00.15%) ── nsPlaceholderFrame
│  │  │  │  │   │  ├──────29,760 B (00.01%) ── sundries [5]
│  │  │  │  │   │  └──────13,440 B (00.01%) ── nsBulletFrame
│  │  │  │  │   ├──16,429,920 B (07.37%) ── style-contexts [5]
│  │  │  │  │   ├──15,523,776 B (06.96%) ── pres-shell [5]
│  │  │  │  │   ├───2,887,680 B (01.30%) ── line-boxes [5]
│  │  │  │  │   ├───1,363,104 B (00.61%) ── style-sets [5]
│  │  │  │  │   ├───1,069,888 B (00.48%) ── pres-contexts [5]
│  │  │  │  │   ├─────373,464 B (00.17%) ── rule-nodes [5]
│  │  │  │  │   └──────16,048 B (00.01%) ── text-runs
│  │  │  │  ├───43,271,792 B (19.41%) -- dom
│  │  │  │  │   ├──29,620,960 B (13.29%) ── element-nodes [5]
│  │  │  │  │   ├──11,846,448 B (05.32%) ── text-nodes [5]
│  │  │  │  │   ├───1,776,800 B (00.80%) ── other [10]
│  │  │  │  │   ├──────16,544 B (00.01%) ── orphan-nodes
│  │  │  │  │   └──────11,040 B (00.00%) ── comment-nodes [3]
│  │  │  │  ├───13,775,360 B (06.18%) -- js
│  │  │  │  │   ├──12,779,328 B (05.73%) -- compartment(http://www.theage.com.au/it-pro/security-it/is-cloud-computing-secure-20120725-22pti.html)
...
│  │  │  │  │   └─────996,032 B (00.45%) -- compartment(http://www.theage.com.au/it-pro/security-it/is-cloud-computing-secure-20120725-22pti.html, about:blank)
...
│  │  │  │  ├────2,598,416 B (01.17%) ── style-sheets [4]
│  │  │  │  └──────────480 B (00.00%) ── property-tables
...
├───36,570,769 B (16.41%) ── heap-unclassified
Created attachment 658387 [details]
about:memory?verbose snapshots (before and after)

Here are the full about:memory?verbose snapshots to which I referred in the previous comment.
Whiteboard: [Memshrink] → [Memshrink:P3]
This appears to be a problem with the site, not with Firefox -- I got very similar growth with Google Chrome.  After 6 hours idle, Chrome's memory consumption rose by ~90MB.  This is comparable with the 107MB rise after 5 hours on Firefox.

Full details from Chrome's about:memory page are below.  I used the site's feedback link to send them a message pointing at this bug.  I don't think we need any more aggressive evangelism.  I'm marking this INVALID because it's a site bug rather than a Firefox bug, but thanks for reporting it, Simon -- better safe than sorry.


-----------------------------------------------------------------------------
initial (~9am)
-----------------------------------------------------------------------------
Summary                                 Memory
Browser                                 Private     Proportional
Chrome                                  152,992k    84,904k

Processes                               Memory
PID     Name                            Private     Proportional
3019    Browser                         31,260k     36,916k
3024    Sandbox helper                   4,504k      2,184k
3029    Zygote                           5,568k        736k
3056    Tab (Chrome) About Memory       14,256k     18,744k
3078    Tab Is cloud computing secure?  73,908k     19,396k
3091    Pepper Plugin Shockwave Flash   23,496k      6,928k
Σ                                       152992k

-----------------------------------------------------------------------------
after 6 hours
-----------------------------------------------------------------------------
Summary                                 Memory
Browser                                 Private     Proportional
Chrome                                  244,844k    83,424k

Processes                               Memory
PID     Name                            Private     Proportional
3019    Browser                         38,828k     37,652k
3024    Sandbox helper                   4,504k      2,184k
3029    Zygote                           5,572k        784k
3056    Tab (Chrome) About Memory       14,324k     16,444k
3078    Tab Is cloud computing secure? 154,720k     19,420k
3091    Pepper Plugin Shockwave Flash   26,896k      6,940k
Σ                                       244844k
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.