823563 - large, growing, memory set and high CPU usage, with add-ons

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[Anand Kumria]

Attachment: moz-memory.txt

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20121212073002

Steps to reproduce:

Open firefox, did a session restore, and browsed as normal


Actual results:

memory consumption increased dramatically (around 4Gb, and counting)


Expected results:

memory consumption should have been relatively constant (around 2Gb)

Comment 1

[Anand Kumria]

When I asked about this on #memshrink, I was pointed to #811228 indicating a problem with firebug.

I have upgraded to firebug 1.11.1; and I still get the high memory and high CPU usage.

Other add-ons are:

adblock plus 2.2.1
english (australian) dictionary 2.1.2
firefox os simulator 1.0
ghostery 2.8.3
google-no-tracking-url 0.5
jsonview 0.7
lazarus form recovery 2.3
rss icon 1.0.6
s3 firefox organiser (s3fox) 0.6
test pilot 1.2.2

and two disabled:
collusion 0.24
flashblock 1.5.15.1


The real killer here is not the excess memory, but the CPU being pegged at 100%; it makes a lot of sites unworkable.

Comment 2

[Anand Kumria]

High CPU usage:

from top:
 3963 anand     20   0 4978m 2.9g  22m R   77 38.8   2754:07 firefox                                                                                                  
Pretty much always 75% or higher.

Comment 3

[Matthias Versen [:Matti]]

You can disable one half of your addons and test. Should be not to difficult to find the addon that is causing this.

Comment 4

[Anand Kumria]

I disabled:

adblock plus 2.2.1
google-no-tracking-url 0.5
jsonview 0.7
s3 firefox organiser (s3fox) 0.6


add-ons are:

english (australian) dictionary 2.1.2
firefox os simulator 1.0
ghostery 2.8.3
lazarus form recovery 2.3
rss icon 1.0.6
test pilot 1.2.2

And 24 hours later things are:

25125 anand     20   0 2743m 1.7g  33m R   90 22.6   1682:30 firefox                                                                                       

So, likely, one of the remaining 6 is the cause of the problem.

Or a bug in Firefox 18 itself

Comment 5

[Matthias Versen [:Matti]]

Try it without ghostery

Comment 6

[Anand Kumria]

Well, I'm doing a normal bisection search.

I've tried for a few days now with:

disabled:

adblock plus 2.2.1
google-no-tracking-url 0.5
jsonview 0.7
s3 firefox organiser (s3fox) 0.6
english (australian) dictionary 2.1.2
firefox os simulator 1.0
lazarus form recovery 2.3

add-ons are:

ghostery 2.8.3
rss icon 1.0.6
test pilot 1.2.2

The usage is still high:

             
 2797 anand     20   0 2107m 1.0g  20m R   65 13.9 472:51.08 firefox                                                                                                    

But certainly not as pronounced.

My guess is that multiple add-ons are leaking memory / CPU.

My next one to disable is ghostery.

Comment 7

[Anand Kumria]

24 hours later, with ghostery disabled and only these enabled:

rss icon 1.0.6
test pilot 1.2.2

I have:

2797 anand 20 0 2160m 1.0g 28m R 66 14.0 757:06.42 firefox

My next guess is to disable rss icon

Comment 8

[Anand Kumria]

About 12 hours later, with rss icon disabled (i.e. only test pilot 1.2.2); I have:

8414 anand 20 0 1676m 708m 31m R 42 9.3 67:30.62 firefox

Memory is still growing, albeit slowly. No surprise, there is a memory leak.

I'd say:
 - at least two extensions have memory leaks; determining which is the issue.

The high-CPU is independent of the add-ons; it appears to be page related.

Unfortunately determining which page does not appear possible (am I mistaken?)

Comment 9

[Edward B]

[testday-20121221] edwardb  (Linux x86-64 )

Started Firefox, and restored previous session.  Then continued to surf as usual.

6 hours later, memory use has been holding at about 35% ~700MB, with CPU usage hovering around 2%.

The add-ons in use are:
+ Video Download Helper v4.9.12
+ DownthemAll! v2.0.15
+ mp3 Download Helper v0.1
+ Mozilla QA Companion v1.2.3
+ FlashGot 1.5.2
+ Feedback 1.2.2

Suggesting the bug status be changed to: RESOLVED, INVALID

Comment 10

[Anand Kumria]

Considering that I have never used, and have never had installed any those plugins; I'd say that your test was invalid.

I can reproduce the problem with these 5 add-ons:
Adblock Plus 2.2.1
English (Australian) Dictionary 2.1.2
Flashblock 1.5.15.1
google-no-tracking-url 0.5
Test Pilot 1.2.2

Comment 11

[Anand Kumria]

Oh, this time is took ~ 48hrs to high 95% CPU usage.

Comment 12

[Anand Kumria]

With the update to Firefox 19 beta, with the same Addons as above (i.e.:

Adblock Plus 2.2.1
English (Australian) Dictionary 2.1.2
Flashblock 1.5.15.1
google-no-tracking-url 0.5
Test Pilot 1.2.2

)

I have, after leaving things on overnight:
 2559 anand     20   0 28.7g 5.0g  13m R   92 67.3   3460:06 firefox                                                                                                    

Yes, 29Gb of virtual memory being used.

At this time, I am still waiting for 'about:memory' (on a New Tab) to respond.

But I can give access to anything in /proc/; from a very quick analysis it appears that there are a large number of of anonymous page maps (from looking in smaps) which are marked as rw-p

Using: http://www.pixelbeat.org/scripts/ps_mem.py, I get different output:

sudo ./ps_mem.py -p 2559
 Private  +   Shared  =  RAM used	Program 

  5.0 GiB +   8.8 MiB =   5.0 GiB	firefox
---------------------------------
                          5.0 GiB
=================================

However Firefox is unresponsive at this time as it is keeping 1 core fully utilised.

Comment 13

[Nicholas Nethercote [inactive]]

Anand, did your bisecting end up clearly blaming a single add-on?

The built-in profiler might be useful too.  You can get instructions here:
https://developer.mozilla.org/en/Performance/Profiling_with_the_Built-in_Profiler

Comment 14

[Mike de Boer [:mikedeboer]]

Adding [wontfix?] due to 5 months of inactivity.

Comment 15

[Wayne Mery (:wsmwk)]

(In reply to Nicholas Nethercote [:njn] from comment #13)
> Anand, did your bisecting end up clearly blaming a single add-on?
> 
> The built-in profiler might be useful too.  You can get instructions here:
> https://developer.mozilla.org/en/Performance/Profiling_with_the_Built-
> in_Profiler

Comment 16

[Nicholas Nethercote [inactive]]

Closing due to lack of response for a long time.