1496148 - High memory use and low responsiveness after long uptime

Status: RESOLVED WORKSFORME

(Firefox :: Extension Compatibility, defect)

Description

[jiri slaby]

Attachment: memory-report.json.gz

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

Steps to reproduce:

I started firefox on 21 Aug. Now, after month and a half of running, firefox consumes 12.8G of virtual memory and 3.9G of RSS. I don't know if that is normal, but to me it looks like too much. I am attaching a memory report. The number of tabs is approximately the same as when started.

Over that time, the responsiveness is decreasing too. I don't know if that is related to the memory pressure or not. Here is the perf profile: https://perfht.ml/2yeb83g

Running with a new profile or without add-ons for such a long time to test this is not much of option. So I hope the memory and perf measurements can pinpoint the problem.


Actual results:

For example writing into the address bar or to this text box does not show characters as I am typing, but later in batches.


Expected results:

Fluent behaviour.

Comment 1

[jiri slaby]

Attachment: about:support output

Comment 2

[Kanchan Kumari QA]

Hello Mike, can you please take a look into the profile? Thanks!

Comment 3

[Mike Conley (:mconley) (:⚙️)]

Definitely the memory usage is related to the sluggish behaviour - looking at the profile, I see the parent struggling to cycle and garbage collect to try to free up space. That's taking cycles from the main threads.

I suspect there might be a leak here in AdBlock Plus (or in the APIs it's using)...

jiri, if you switch (temporarily) to using uBlock Origin, do you see the same behaviour?

Comment 4

[jiri slaby]

(In reply to Mike Conley (:mconley) (:⚙️) from comment #3)
> Definitely the memory usage is related to the sluggish behaviour - looking
> at the profile, I see the parent struggling to cycle and garbage collect to
> try to free up space. That's taking cycles from the main threads.

Which reminds me that "Minimize memory usage" did not lower the memory usage at all. That makes sense.

> I suspect there might be a leak here in AdBlock Plus (or in the APIs it's
> using)...
> 
> jiri, if you switch (temporarily) to using uBlock Origin, do you see the
> same behaviour?

Switched to ublock, now give me ~ 2 weeks to reproduce :).

Comment 5

[jiri slaby]

(In reply to jiri slaby from comment #4)
> Switched to ublock, now give me ~ 2 weeks to reproduce :).

I had to reboot yesterday and forgot to take a look on the memory consumption.

The feeling (responsiveness) was good though.

Comment 6

[jiri slaby]

It looks promising with uBlock. It is running since 19 Oct, and the 5 firefox threads eat each 500-700MB of resident memory.

So what next? (I keep it running.)

Comment 7

[Mike Conley (:mconley) (:⚙️)]

Hey evilpie, do you know if there's a tracking bug for ABP memory bugs?

Comment 9

[Wayne Mery (:wsmwk)]

jiri, is this issue gone for you?

Comment 10

[jiri slaby]

Likely.