Memory creep/leak concern in the Fx37 64-bit beta builds

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
4 years ago
3 years ago

People

(Reporter: ChrisG683, Unassigned)

Tracking

37 Branch
x86
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink:P3])

Attachments

(3 attachments)

(Reporter)

Description

4 years ago
Created attachment 8578924 [details]
Firefox Troubleshooting Info.txt

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

Steps to reproduce:

Using Firefox with fairly light browsing habits (standard web pages, light amounts of videos).  I leave the browser open at work and don't close it unless I need to.

As a little history briefing, I started using the 64-bit build a little under a year ago when they were available for Nightly.  While it ran fine, I noticed that my memory usage would easily eclipse 4 GB after being open for a few days.  After many months of disabling add-ons, making a new profile, etc, I discovered that switching back to the 32-bit builds fixed my issue.  Clearly either there was either a major problem with the 64-bit builds (hence Nightly), or I had some weird add-on memory leak.

Now that the 64-bit builds have graduated to beta I decided to try them out again, and to my dismay I still seem to be having memory spike issues (although they don't seem to be as bad).


Actual results:

The amount of time varies, but over the course of a day, my memory usage creeps up.  When I start the browser fresh, I sit at around 500-700 MB depending on the amount of pages I have open.  Right now it's been open for a couple of days and I'm sitting at ~1.2 GB with only 3 tabs open, none of which are media intensive webpages (or any more intensive than I normally use)


Expected results:

When I run the same profile on the 32-bit beta, I start at around 450-650 MB, and usually don't go over 700-800 MB after being open for a week.

I have attached my Firefox troubleshooting info to this bug.

You can access my about:memory log here:
https://drive.google.com/open?id=0B4KtJAZ-pKFqbS0xQTZ1Z2swZ3c&authuser=0

You can access my about:ccdump log here:
https://drive.google.com/open?id=0B4KtJAZ-pKFqbmsxVWtfdFpaV0U&authuser=0
(Reporter)

Comment 1

4 years ago
Created attachment 8578926 [details]
memory-report.json.gz

Comment 2

4 years ago
Thanks for the report and for the about:memory dump!

You still have many addons and 6 ghost-windows, which indicate you do have leaks. Statistically, this happens primarily because of add-ons. Please try https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems first.

64-bit is expected to use more memory, although I'd be surprised if you had leaks with 64-bit, but not with 32-bit using the same profile...
Flags: needinfo?(ChrisG683)
Whiteboard: [MemShrink]
Yeah, your 32-bit memory usage is increasing by ~150-350MB, and your 64-bit memory usage is increasing by ~600MB or so, which is roughly consistent with objects being ~2x as large on 64-bit.

Have you tried disabling some or all of the addons to see if memory usage improves  and/or identifying which addon is causing the problem?
Whiteboard: [MemShrink] → [MemShrink:P3]

Comment 4

3 years ago
Created attachment 8600699 [details]
memory-report.json.gz

The memory usage ends up to 1GB. The FireFox 37.0.2 client needs to be restarted.
Chris, are you still experiencing this issue on the latest Firefox versions (currently Firefox 43, Nightly 46)?
https://www.mozilla.org/en-US/firefox/new/
https://nightly.mozilla.org/

If yes, did you had the time to try the suggestions from Comment 3?
Closing this as incomplete due to lack of additional information from the reporter.

Chris, please feel free to reopen it if you still have the problem reproducible (on the latest release) and you can provide additional details that could help us reproduce or identify your issue.

Thanks!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(ChrisG683)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.