New issue
Advanced search Search tips

Issue 730437 link

Starred by 7 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Extension's memory usage keeps growing until opening browser action popup

Reported by sebast...@adblockplus.org, Jun 7 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Install Adblock Plus or AdBlock 
2. Go to youtube.com and start playing any playlist (there are other ways to reproduce but this seems to be the most reliable so far)
3. Check memory usage of the extension's background page in Chrome's Task Manager
4. Wait for 1h-24-h
5. Check memory usage again
6. Click the browser action icon bringing up the popup
7. Wait a minute after the browser action icon has been closed again
8. Check memory usage again

What is the expected behavior?
The memory usage should remain stable.

What went wrong?
The memory usage keeps growing, in my case it started off at ~120MB and grew to ~160MB in 1h. It seems to continue growing as others report even larger memory usage after 24h [1].

Interestingly, and this indicates that it might be a Chrome bug rather than a memory leak on our end, the memory usage goes back to normal after you open the browser action popup.

I took heap snapshots, and it seems the difference in memory usage, before and after opening the browser action popup corresponds to the retained size of the background page's window object, see the attached screenshot. However, when I expend the object in the profiler, none of the contained objects have any notable size. Furthermore the Statistics view in the profiler indicates that the additional memory usage comes from System objects.

[1]: https://issues.adblockplus.org/ticket/5291

WebStore page: 

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: n/a
OS Version: 
Flash Version:
 
Screenshot from 2017-06-07 08-15-49.png
253 KB View Download
Labels: Needs-Triage-M58
We further looked into it, see the discussion in the Adblock Plus issue linked above, and we have strong indications that the problem here is Chrome indefinitely delaying garbage collection.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 18 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
it seems that its still happening
Still happening
Is there a way to reopen this? It's still happening and lack of response from chromium.org in the absence of a "waiting for feedback" (implying it's a live issue that just didn't get a response from the project) shouldn't result in an archive...

Sign in to add a comment