User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20180315233128 Steps to reproduce: Start Firefox....leave running (open) Actual results: I have Firefox open at this time with 8 windows open currently. When I started it up Task manager showed 480MB of memory used as I am writing this the memory used is 716.8 MB and counting (up) ...and now 727MB 10 minutes later it was well over a gig byte earlier with another set of pages loaded that had been open over night. It does move up and down ....but generally up Expected results: After pages load and initial content downloads/cookie writing and other spy-where type stuff is done with. The memory usage should stay at about the same. No data gathering loggers etc. should be going on either. ( I don't know if this is a problem with Firefox or security with loaded content. I do notice in Process Explorer that I/O writes are creeping up also when i would think they shouldn't be ie. no new content etc... )

mxdog, 8 windows opened? And not 8 tabs? Are those 8 windows each with 1 tab and with 1 empty blank page? Please elaborate. > other spy-where type stuff Can you name those anti-spyware softwares? Have you read/Can you read Firefox uses too much memory (RAM) - How to fix https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram and see if that helps...

8 windows open various tabs on various sites I never said they where empty. Cookies are by definition (collecting information and reporting back without knowledge or approval)...was being facetious there sorry. Forgot no sense humor on bug sites. And I'm not reporting this as it is using to much memory, but that the memory seems to be creeping up with no activity on my part. Slowly...but creeping I have attached 2 logs. They where created with a few windows up and after going to about:memory and doing a garbage cleaning GC and then CC. you can compare the file creation to get the time differance. ( no FF windows touched except this one ) I doubt this is relevant:but in task manager I am also showing GPU 0-3d in the GPU Engine column and I don't see any obvious flash or other content that would use it.

Memory profiling and leak detection tools https://developer.mozilla.org/en-US/docs/Mozilla/Performance#Memory_profiling_and_leak_detection_tools I will let someone else triage this bug report as this is not my cup of tea.

Hi mxdog, Thanks for reporting the issue. Per Comment 2, how many tabs were opened on your various windows? I'm trying to see if the memory issue is coming from the various tabs or the various windows.

I have no idea.. guess-ta-mat from the memory dump time ...4-5 windows 8-10 total tabs. I just got an update on firefox so no clue if it would be the same if i tried to reproduce. The over night to almost a gig of usage was the one that triggered my report ...I think there where 4 windows and maybe 8 tabs. as soon as I killed them and reloaded was easily half that. All i did the next day was open up a few web sites mostly, stackexchange stuff. open task manager ..made a note of mem usage and worked away awhile with those just sitting there and just watched it steady if slowing tick up.

Counting up fast with these hanging

This may help ...I just noticed that i have some dead tasks in FF and its counting up faster then normal 40 MB in 9 minutes. attached is a .jpg of task manager I only actually have 2 window open 1 tab each ..this site being one and google search results in another. so maybe as I am closing windows FF isn't killing itself and flushing ? at 380 now and fast counting up ..started at 340 ..9 minutes ago.

I also have this problem. I have to restart Firefox multiple times a day, as it eats over 6 gigs of RAM. Linux and Windows both. No extensions, only plugins are OpenH264 and Widevine.

As I typed the previous comment, my RAM usage was under 4 gigs. Simply switching back to the OligoAnalyzer tab shot it up to nearly 6 gigs. http://www.idtdna.com/calc/analyzer

ebs15242, that idtdna.com site has a lot of minified style sheets and an unusual amount of javascript, including minified javascript. From experience, I would not be surprised at all if RAM usage would dramatically increase when visiting that site. - - - - - There are already many bug reports with memory leakage. What's helpful is to find the *_exact steps_* by which the problem can be reproduced. We do not have such steps in this bug report.

" If you are reporting a memory use or leak bug, please attach the output of about:memory https://developer.mozilla.org/en-US/docs/Mozilla/Performance/about:memory Ideally, find steps to reproduce an increase in what is shown in about:memory (even after clicking the 'Minimize memory usage' button at the bottom). If you have trouble finding steps to reproduce, try the Firefox Support page titled Firefox Uses Too Much Memory (Ram) - How to Fix https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram. " https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines

The memory report from comment 11 shows a ton of ghost windows, whereas I can't spot anything in the reports from comment 3 and comment 4.

Every bug report should have clear and explicit steps to reproduce. We do not have this in this bug report. Every bug report should be about 1 and only 1 issue and a set of steps. Otherwise, this becomes unworkable for software developers. Bug writing guidelines How to report a bug Other details you should heed https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines#Other_details_you_should_heed And searching for duplicate is also a task that needs to be done; bug triagers can help. There are already a lot of bug reports regarding sites that trigger or cause a) huge memory usage, b) memory leakages, c) memory usage growing, etc... ebs15242, from my experience, that idtdna.com site is most likely a website that abuses user system resources, that resorts to an insane amount of scripts (setTimeout, setInterval).

Can you attach a memory report from when you're experiencing an issue? As-is the memory usage looks as expected.

Closing for now, feel free to reopen if you can gather the requested memory reports.