farluiz Reporter
	Description • 9 years ago

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150807085045

Steps to reproduce:

Open the following site in any TAB:

http://esporte.uol.com.br/futebol/campeonatos/brasileirao/jogos

Do anything! Only track Firefox memory usage.



Actual results:

The Firefox memory usage quickly increases steadily until eventually OOP. Firefox becomes somewhat unresponsive when the memory usage exceeds 1GB.


Expected results:

Some increase in Firefox memory usage is acceptable but not endless increase with only one TAB openned!

I tested with Firefox 39 and 40, on Windows 7 32 bits and Windows 8.1 64 bits with the same results.

	Simona Badau, Desktop QA
	Comment 1 • 9 years ago

Mozilla/5.0 (Windows NT 6.3; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20151204030208

Works fine for me on the latest Nightly version.

Farluiz, are you still experiencing this issue on the latest Firefox version? 

Please can you confirm whether this issue is still reproducible when you start Firefox with a new profile?
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

	farluiz Reporter
	Comment 3 • 9 years ago

(In reply to Simona B from comment #1)
> Mozilla/5.0 (Windows NT 6.3; rv:45.0) Gecko/20100101 Firefox/45.0
> Build ID: 20151204030208
> 
> Works fine for me on the latest Nightly version.
> 
> Farluiz, are you still experiencing this issue on the latest Firefox
> version? 
> 
> Please can you confirm whether this issue is still reproducible when you
> start Firefox with a new profile?
> https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-
> firefox-profiles

Yes. Always reproducible in all computers!!! This issue occurs in all Firefox versions including version 42. I already reported this problem to about three years. It's very easy to reproduce. I produced a "OOP" right now especially for you. What I did:

1) Opened Firefox 42 with a new Profile;
2) In the unique tab open I opened that site: http://esporte.uol.com.br/futebol/campeonatos/brasileirao/jogos/;
3) No interaction with the site was made. I just waited;
4) I started to monitor Firefox memory usage with MS POWERSHELL.

Firefox memory usage increases steadily. Look in the attachment "firefox_mem_usage.txt". Watch the columns PM (Private Memory) and WS (Working Set). The numbers go up constantly. When Firefox surpasses 2GB of allocated memory (it's a x64 computer), the numbers becomes negative. When Firefox nears 4GB of memory, it crashes.

I started the Firefox process today (dec/04/2015) 14:46 (02:46 PM). After more or less 2 hours, Firefox crashed with the following crash ID: bp-72def6b5-1029-4d3f-9fe5-b51312151204.

In x86 computers (2GB), the crash is much faster.

My computer:

Intel x64 Broadwell 5500U processor
8GB RAM
Windows 64 8.1
Nvidia Geforce 820M + Intel Graphics 5500U.

Luiz

PS: The high memory usage also occurs with others browses, but these does not crashes!

	farluiz Reporter
	Comment 4 • 9 years ago

Its OOM not OOP. Sorry, my mistake. There are many acronyms in my head.

Luiz

	Simona Badau, Desktop QA
	Comment 5 • 9 years ago

I can confirm that Firefox 42 is crashing when following the indications from Comment 3 (it took me a little over 2 hours). Like mentioned in Comment 3, the memory usage increases until Firefox crashes.

bp-38f2f860-fc34-4d4d-991e-a8f562151207

	Timothy Nikkel (:tnikkel)
	Comment 6 • 8 years ago

I opened http://esporte.uol.com.br/futebol/campeonatos/brasileirao/jogos in a tab and left it for about 30 minutes. This is a diff from a memory report from before to after.

964.52 MB (100.0%) -- explicit
├──903.52 MB (93.68%) -- window-objects
│  ├──903.20 MB (93.64%) -- top(http://esporte.uol.com.br/futebol/campeonatos/brasileirao/jogos/, id=NNN)
│  │  ├──902.76 MB (93.60%) -- active
│  │  │  ├──902.86 MB (93.61%) -- window(http://esporte.uol.com.br/futebol/campeonatos/brasileirao/jogos/)
│  │  │  │  ├──906.18 MB (93.95%) -- dom
│  │  │  │  │  ├──906.19 MB (93.95%) ── orphan-nodes
│  │  │  │  │  └───-0.01 MB (-0.00%) ++ (2 tiny)
│  │  │  │  └───-3.33 MB (-0.34%) ++ (3 tiny)
│  │  │  └───-0.09 MB (-0.01%) ++ (9 tiny)
│  │  └────0.43 MB (00.04%) ++ js-zone(0xNNN)
│  └────0.32 MB (00.03%) ++ (8 tiny)
├───40.28 MB (04.18%) ── heap-unclassified
├───23.12 MB (02.40%) -- heap-overhead
│   ├──21.63 MB (02.24%) ── bookkeeping
│   └───1.48 MB (00.15%) ++ (2 tiny)
└───-2.39 MB (-0.25%) ++ (13 tiny)

All orphan nodes. This suggests the page is keeping around (leaking?) unused nodes.

	Nicholas Nethercote [inactive]
	Comment 7 • 8 years ago

This is definitely a leak caused by the site. I left the site open for an hour
or so in both Firefox and Chromium and took multiple memory measurements along 
the way. In Firefox's about:memory the final measurement was this:

> │  ├──2,631.38 MB (86.63%) --
> top(http://esporte.uol.com.br/futebol/campeonatos/brasileirao/jogos/, id=8)
> │  │  ├──2,626.01 MB (86.45%) -- active
> │  │  │  ├──2,621.44 MB (86.30%) --
> window(http://esporte.uol.com.br/futebol/campeonatos/brasileirao/jogos/)
> │  │  │  │  ├──2,577.14 MB (84.84%) -- dom
> │  │  │  │  │  ├──2,571.14 MB (84.64%) ── orphan-nodes
> │  │  │  │  │  └──────6.00 MB (00.20%) ++ (5 tiny)

In Chromium's about:memory (a.k.a. chrome://memory-redirect/) the final
measurement was this:

> PID 3172 Tab
> Campeonato Brasileiro 2015 - Classificação e jogos - UOL Esporte
> 1,739,212k  78,664k

Not quite as high as Firefox -- maybe Chromium's DOM node representation is slimmer
-- but it was clearly growing at a similar rate.

	Nicholas Nethercote [inactive]
	Comment 8 • 8 years ago

I tried using Firefox's memory profiler to investigate, but it said 91% of the JS objects didn't have an allocation stack. Maybe it doesn't measure DOM nodes.

	Nicholas Nethercote [inactive]
	Comment 9 • 8 years ago

I tried using Google Translate to find a webmaster email address, but failed. 

farluiz, if are able to email someone responsible for the site and tell them about this problem (i.e. point them to this bug report, especially comment 7) that would be very helpful. Thank you.

	farluiz Reporter
	Comment 10 • 8 years ago

(In reply to Nicholas Nethercote [:njn] from comment #9)
> I tried using Google Translate to find a webmaster email address, but
> failed. 
> 
> farluiz, if are able to email someone responsible for the site and tell them
> about this problem (i.e. point them to this bug report, especially comment
> 7) that would be very helpful. Thank you.

Yes. I will try to contact the site developer (UOL.COM.BR, a very big company), explain the problem and request the page fix. After, I come back here to report the result. Thanks!

	farluiz Reporter
	Comment 11 • 8 years ago

I reported that issue to UOL.COM.BR on 01/14/2016 and I'm still awaiting a response.

	farluiz Reporter
	Comment 12 • 8 years ago

Email sent again on 01/20/2016. No response so far from UOL.COM.BR.

	Sylvestre Ledru [:Sylvestre]
	Comment 13 • 6 years ago

Closing because no crash reported since 12 weeks.

	Sylvestre Ledru [:Sylvestre]
	Comment 14 • 6 years ago

Closing because no crash reported since 12 weeks.