Potential memory leak after browsing some websites, related to audiodg
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
People
(Reporter: maximiliankohlr+bugzilla, Unassigned)
Details
(Keywords: memory-leak)
Attachments
(1 file)
190.57 KB,
application/gzip
|
Details |
Updated•7 years ago
|
Reporter | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
Reporter | ||
Comment 6•7 years ago
|
||
Reporter | ||
Comment 7•7 years ago
|
||
Updated•7 years ago
|
Reporter | ||
Comment 8•7 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Comment 9•4 years ago
|
||
Maximilian, can you still reproduce this?
Reporter | ||
Comment 10•4 years ago
|
||
I built a new PC with double the RAM (16 Gig) and haven't noticed any issues. Looking right now I have 10GB in use, 5.4 available, 5.3 cached. 770MB paged pool, 615MB non-paged. 25/29 GB committed. 10+ firefox processes totaling around 4,000 MB. Showing 66% memory use on processes tab.
Looking at my previous messages it seems Balabolka may have been implicated, and I haven't used that program in a long time. So I tested it out.
I left Balabolka on overnight and now the memory use is at 77% vs 66%. Firefox is using 12 different processes and about 4,800 MB. Balabolka had finished reading the book when I got to it. When I closed it the memory usage started slowly decreasing into the 60's (then went back up to around 77% when I activated a browser-based game in Chrome).
Windows Audio Device Graph Isolation is 4th highest mem usage at 656 MB.
Memory performance tab is about the same for non-paged pool and paged pool. Cached went down to 3.6, available down to 3.6. In use up to 12.3. Committed up to 29/33.
Chrome is on 13 processes and about 1200 MB. I started playing a browser-based game in Chrome and it raised to 1900 MB.
Now that I think of it, perhaps the leak is more of an audio device leak rather than Firefox, and perhaps Firefox just uses significantly more memory than Chrome by default. But then I recall the memory being freed up by closing my browser. I'll do that and report back.
Well, before I could close Firefox, the browser-based Chrome game caused Chrome to freeze up temporarily, and the game had to be refreshed, and that seemed to reset all the memory statuses to what they were last night. Firefox dropped even lower to about 3,500 MB (down from 4,800 without changing anything in Firefox). Total mem usage is 65% (with the Chrome game active). Windows Audio Device Graph Isolation is nowhere near the top. Chrome is still around 1800 with the game active.
Comment 11•4 years ago
|
||
So sounds like not a Firefox bug. Thanks for the info
Description
•