Closed
Bug 1414661
Opened 8 years ago
Closed 5 years ago
Memory usage in Quantum
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
| Tracking | Status | |
|---|---|---|
| firefox57 | --- | affected |
People
(Reporter: lewbjob, Unassigned)
Details
Attachments
(1 file)
|
169.15 KB,
application/x-gzip
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20100101
Steps to reproduce:
* Firefox 57.0b14
Addons:
* Cookie Auto Delete
* Decentraleyes
* UBlock Orgins
* Privacy Badger
* HTTPS Everywhere
Actual results:
* 207.70 MB (100.0%) -- explicit
* 134,217,727.94 MB (100.0%) -- address-space
I have tried new profile. With 2-3 tabs open memory will get over 1 gig of usage with cpu above 50%. I'm also getting a lot of Page taking a long time to load messages asking if i want to wait or kill.
Expected results:
Memory usage shouldn't be over a gig with under 4 tabs
Updated•8 years ago
|
Component: Untriaged → Memory Allocator
Product: Firefox → Core
Updated•8 years ago
|
status-firefox57:
--- → affected
Component: Memory Allocator → General
Comment 1•8 years ago
|
||
> * 207.70 MB (100.0%) -- explicit
This is a very reasonable and typical value.
> * 134,217,727.94 MB (100.0%) -- address-space
This tells you how much address space the entire system has, not how much Firefox is using.
> I have tried new profile. With 2-3 tabs open memory will get over 1 gig of
> usage with cpu above 50%. I'm also getting a lot of Page taking a long time
> to load messages asking if i want to wait or kill.
Where did you get the "1 gig" measurement from?
I can believe that you are having performance problems, but judging from the memory report the memory usage is fairly reasonable.
Comment 2•8 years ago
|
||
I have the same issue, but it seems to be happening when i open several facebook pages with video.
I also get at the same time an error of memory shortage from windows.
Disabling e10s seems to partially solves this (browser.tabs.remote.autostart to false).
Another fix is to set dom.ipc.processCount and dom.ipc.processCount.webLargeAllocation to 2.
By applying one of these 2 fixes, pages keep loading, rather than giving up.
Comment 3•8 years ago
|
||
If you go to the windows task manager (ctrl-alt-delete), and look at the background processes. You get one process of 800mb for firefox.exe next to several other firefox.exe background processes. I got 2gb in my pc and i get memory shortage errors.
This might be the memory consumption that lewbjob@yahoo.com repported.
That number reaches over 50% CPU usage and over 1,000 mb with less than 4 tabs open. None of which have video content of any kind. Have to go through about:memory to release ram from closed tabs. Also have to frequently close Firefox through Task manager due to freezing. Have 4gig of ram installed.
Comment 5•8 years ago
|
||
On my pc, i have the same issue.
I do see more problems with addons like ghostery, uBlock, privacy badger or disconnect. When I try to close my browser, the memory keeps locked on shutdown and firefox only closes after several seconds. So this might be interesting route to investigate.
First I saw the issue with ghostery and I tried to replace it with privacy badger or disconnect, but all exhibit issues with memory 'locking' on shutdown.
For adblocking, Adblocker Lite seems to exhibit the least issues with memory usage.
I have not found an alternative for ghostery. Ghostery doesn't exhibit these issues on chrome.
Comment 6•8 years ago
|
||
Steps to reproduce:
1. open several pages in firefox on a pc with 2 gigabyte in firefox with ghostery (or privacy badger or disconnect)
2. open task manager and look for background processes
Result
Firefox keeps running several seconds when addons are installed
Expected
Background processes firefox.exe close directly / reclaim memory.
Comment 7•8 years ago
|
||
I opened a separate issue for the video issue with number 1421186.
Updated•5 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Flags: needinfo?(lewbjob)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•