Closed Bug 1181753 Opened 9 years ago Closed 8 years ago

Excessive memory size and continous growth

Categories

(Core :: Graphics, defect)

39 Branch
Unspecified
All
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: bernie, Unassigned)

Details

(Whiteboard: [gfx-noted])

Attachments

(8 files)

Attached file about_support.txt
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150630154324

Steps to reproduce:

Run Firefox 39 and leave it open for several hours with a few tabs and a few windows.


Actual results:

Excessive and continuous growth of memory usage.  Right now, after running for about 4 1/2 hours Firefox 39 is using 1,085,400K and continuing to grow.


Expected results:

Seems like Firefox should not continue to grow memory usage even when no user iniated activity.  Runnig with add-ons disabled does not solve the problem.  

This seems related to Bug 1137251, but that bug is closed and I was asked to open a new bug report.

I'm attaching reports from about:support and from about:memory
Attached file memory-report.json.gz
Component: Untriaged → Graphics
Product: Firefox → Core
I don't know that this is graphics, but we can start there.  We have failures to get some large textures (22k x 176) in the log, and we have this:
   "path": "d3d11-shared-textures",
   "kind": 2,
   "units": 0,
   "amount": 85984320,
   "description": "Memory used for D3D11 shared textures"

In the meantime, Bernie, if you have a chance, could you rerun the same test with a clean profile and all the add-ons disabled.  I understand there are assertions that this has nothing to do with add-ons (e.g., bug-1137251-comment-62), but it would be good to be able to compare the results.

Also, are you just having the browser sit there on the new tab page, or are you using it during these 4+ hours?
Flags: needinfo?(bernie)
I understand we only have reports from Windows (on the other bug), but I'll leave it as all platforms for now.
OS: Unspecified → All
Also, if you turn off hardware acceleration in the preferences, are the results any different?
Milan, you'll have to remind me how to start Pirefox with a clean, alterante profile so that I don't lose my current profile.  I haven't had to do that since Netscape days.

Also, if you tell me how to turn off the hardware acceleration preference I can try that.
Flags: needinfo?(bernie)
The easiest way is to duplicate a shortcut to firefox, open the properties for it, and add -P to the target value.  So, it would look something like this by the time you are done:
"C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -P
Run that shortcut, and you will get a window that lets you create a new profile; once you create it, you will probably want to uncheck the "use this as the default without asking" for this new profile.  Once you're done testing, you can just remove that profile.
Once you have that profile running, the hamburger menu on the right will let you open "Options", and the "Advanced" tab would let you uncheck "Use hardware acceleration when available".  This change would be specific to the newly created profile.

Sorry, I'm giving you instructions for the English version, just do the matching thing if you are running a localized version.
From a clean profile with no add-ons, no sync, no problem, for comparison.
From clean profile, no addons, no sync, no problem, for comparison.
I've been running with a clean profile, no addons, no sync, hardware acceleration off, for two days and the problem has not recurred.  Memory has grown and shrunk, when I've noticed, between about 330,000K and 700,000K.  Flash has failed several times and one time seems to have hung Firefox but that is a different problem.

I've posted a current Support and Memory report for comparison, both with "clean" at the end of the filename.

Not sure what to try next since the problem had occurred with all add-ons disabled.
If you just enable hardware acceleration, but stay without the add-ons, does the problem come back?
No, turning on hardware acceleration does not seem to cause the problem.
That would suggest a problem with one of the add-ons, a combination of add-ons, a combination of an add-on with hardware acceleration.  It would take some time to verify which one of these it would be, by leaving hardware acceleration enabled, and in turn enable add-ons one by one, to see if it's the add-on + acceleration.  If you find one, then try it with the same add-on, but without hardware acceleration.  If this doesn't reveal the problem, then you get a combinatorial explosion of having to look at a combination of add-ons, which would take even longer to sort out.
If you do have a chance, and can get some of this data, we can take it from there.
I am going to start trying that with the add-ons.  Observations this week with the original profile make it seem like a major factor is that storage is not being released properly.  I can open several tabs, or a few windows and storage gets bigger as expected and then continues to grow but does eventually stop growing.  As tabs or windows are closed storage utilization gets a little smaller, but not nearly what it was before the tabs were opened and closed.  I'm seeing a difference in the range of 500,000K.
I've been having a Firefox memory leak problem for a while.  Attached is an about:memory output with plug-ins enabled.  Do I now need to proceed to test with plug-ins disabled?

I'm looking at Firefox's memory use via Process Explorer. Is it "Working Set" or "Private Bytes" that I should be paying attention to?
Whiteboard: [gfx-noted]
Attached file about-support.txt
Providing about:support, about:plugins and about:memory.
Many thanks for investigating this very annoying problem.
Please let me know if you require any further information.
Attached file about-plugins.txt
Providing about:support, about:plugins and about:memory.
Many thanks for investigating this very annoying problem.
Please let me know if you require any further information.
Attached file memory-report.json.gz
Providing about:support, about:plugins and about:memory.
Many thanks for investigating this very annoying problem.
Please let me know if you require any further information.
Should [MemShrink] be added to the Whiteboard in this Bug?  (Can't figure out how to do it myself.)
(In reply to Bernie from comment #13)
> I am going to start trying that with the add-ons.  Observations this week
> with the original profile make it seem like a major factor is that storage
> is not being released properly.  I can open several tabs, or a few windows
> and storage gets bigger as expected and then continues to grow but does
> eventually stop growing.  As tabs or windows are closed storage utilization
> gets a little smaller, but not nearly what it was before the tabs were
> opened and closed.  I'm seeing a difference in the range of 500,000K.

which addon?
Flags: needinfo?(bernie)
Flags: needinfo?(bernie)
closing based on comment 12
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: