Closed Bug 1293965 Opened 8 years ago Closed 8 years ago

Memory consumption increases on a page that refreshes (500MB per quarter hour)

Categories

(Core :: General, defect)

51 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: newsmails, Unassigned)

Details

(Whiteboard: [MemShrink])

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20160809030200

Steps to reproduce:

NB: the page to reproduce concerns the Olympics in Rio in 2016 ==> limited time to reproduce?

1- go to http://www.eurosport.fr/jeux-olympiques/rio/2016/liveevent.shtml
2- leave this page open (in my case, it does not have the focus and is often in the background)



Actual results:

I see 2 firefox process in Task Manager:
-one which remains at its initial memory size
-the other who grows up to saturate the memory (~500Mo per 15 minutes)

an observation : when I quit this page, the size of the ram doubles before the memory dicreases...
51.0A1 (2016-08-09)


Expected results:

The memory usage should not change on a simple page which refreshes.


Tested on windows 7 64
With firefox nightly (51.0A1 (2016-08-09)) in SAFE mode. 

An old bug has the same subject :
Bug 330608 - Memory usage increases everytime page refreshes.
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Idem on linux (kernel 4.6.0) with firefox 45.3.0 ESR

Note : 
the almost doubling of the ram when leaving the page is a problem: if firefox uses 2.5 GB of RAM and you have 4 GB, it'll swap...
Another test on Windows 7 64 :
- idem with Seamonkey 2.40
- no problem with Internet Explorer 11
Hello,

Thanks for reporting the bug,

I can reproduce the issue with the following specs:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
Status: UNCONFIRMED → NEW
Component: Untriaged → General
Ever confirmed: true
Product: Firefox → Core
Whiteboard: [MemShrink]
I see orphan nodes increasing as I leave this page open. Making me suspect the page is leaking nodes.
If you close the tab, do we get a detached or ghost window?  If so, it could be helpful to see the verbose gc/cc logs from about:memory.  (Don't post them here, but you can email to me.)
I don't see any ghost or detached windows after closing the tab (and waiting).
I'll take a look at the memory usage breakdown.
Flags: needinfo?(erahm)
I ran overnight and couldn't repro. I'm going to close for now, but if we can reproduce getting a memory report would be helpful.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(erahm)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.