User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.98 Safari/537.36 Vivaldi/1.6.689.46 Steps to reproduce: Activate "Disable HTTP cache" in the console settings. Refresh any page. Happens on version: 52 and up. Actual results: The stack starts building up like normal, but when it releases memory not all of it is released. Expected results: The stack should have been released without any memory hanging behind. (This causes the memory to go up to 3~ GB in only an hour or so)

Michal, Honza?

Looks like a wrong summary. The leak obviously isn't in http cache when it has to be disabled to reproduce the leak.

I am sorry if I didn't explain it well enough. However isn't it weird that the moment you "disable" a cache it starts leaking (building up)? All I managed to find out that it is related to disabling the HTTP cache option. (Any tips what I should do different to make a more clear bug report?)

Are you 100% sure this leak doesn't appear on Firefox 51? Just to make sure the is no add-on influence, can you try with a clean profile? > Activate "Disable HTTP cache" in the console settings. This is devtools. I think someone from them should look first. This report is too general to say where exactly is the problem. moving to a a different component.

All tests were done on cleanly installed firefoxes, so I don't think the profile can get any cleaner? I couldn't find a firefox 51 for Arch Linux x64, I already struggled to find a 52 one. I first noticed it at version 54.x and found a 52 binary and it still was in there.

(In reply to tehber from comment #5) > All tests were done on cleanly installed firefoxes, so I don't think the > profile can get any cleaner? OK, was not clear from the report. > I couldn't find a firefox 51 for Arch Linux x64, I already struggled to find > a 52 one. Not sure if arch linux needs a special build, but here you may at least try finding an older build: http://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-release-l10n/ (a very long list, includes all archs and l10s)

Right, I managed to build Firefox 46 and even there it appears to leak memory once you disable the HTTP cache. That was the earliest version I saw on the FTP and figured why not try that. All I had to do was disable HTTP cache via the console settings then press F5 a few times and watch as it chunks away at my memory. Anything else I can try?

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Moving this inactive P2 to the backlog (P3)