address-space memory leak
Categories
(Core :: Performance, defect)
Tracking
()
People
(Reporter: dominic.parry, Unassigned)
Details
Attachments
(1 file)
|
121.05 KB,
application/x-gzip
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
Open firefox developer edition 110.0b3 (64-bit) and keep it running for about an hour - it should keep on building upwards with even just a single tab to 4GB of memory usage.
Actual results:
There seems to be a memory leak within address-space with by far the largest memory use.
This is indicative of that:
140,737,488,289,792 B (100.0%) -- address-space
├──103,346,166,456,320 B (73.43%) ── free(segments=572)
├───37,390,304,555,008 B (26.57%) -- reserved
│ ├──35,191,331,536,896 B (25.00%) ── private(segments=1129)
│ └───2,198,973,018,112 B (01.56%) ── mapped(segments=18)
└────────1,017,278,464 B (00.00%) -- commit
├────402,845,696 B (00.00%) -- image
│ ├──245,915,648 B (00.00%) ── execute-read(segments=197)
│ ├──131,571,712 B (00.00%) ── readonly(segments=598)
│ ├───21,766,144 B (00.00%) ── writecopy(segments=148)
│ └────3,592,192 B (00.00%) ── readwrite(segments=310)
├────325,750,784 B (00.00%) -- private
│ ├──321,810,432 B (00.00%) ── readwrite(segments=1083)
│ ├────2,023,424 B (00.00%) ── readwrite+stack(segments=82)
│ ├────1,155,072 B (00.00%) ── readwrite+guard(segments=82)
│ ├──────733,184 B (00.00%) ── execute-read(segments=6)
│ ├───────16,384 B (00.00%) ── readonly(segments=3)
│ ├────────8,192 B (00.00%) ── noaccess(segments=2)
│ └────────4,096 B (00.00%) ── execute-readwrite(segments=1)
└────288,681,984 B (00.00%) -- mapped
├──213,102,592 B (00.00%) ── readonly(segments=310)
├───66,048,000 B (00.00%) ── noaccess(segments=125)
├────9,232,384 B (00.00%) ── readwrite(segments=116)
├──────294,912 B (00.00%) ── writecopy(segments=1)
└────────4,096 B (00.00%) ── execute-read(segments=1)
Expected results:
It should have not even kept going up and increasing the heap size of the address-space. I have attached the memory report.
|
||
Updated•1 year ago
|
|
||
Comment 1•1 year ago
|
||
So are you actually seeing high memory usage, or just high number for the address space?
|
Reporter | |
Comment 2•1 year ago
|
||
(In reply to Olli Pettay [:smaug][bugs@pettay.fi] from comment #1)
So are you actually seeing high memory usage, or just high number for the address space?
High memory usage, seemingly caused (according to about:memory) by the address space.
Don't know why it kept going up. I have 16GB Ram, and firefox was using 7-8GB with only one tab open.
I say it in past tense as I haven't used firefox as of recent. I can give it another shot if needed.
|
||
Comment 3•8 months ago
|
||
A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Closing the bug as incomplete.
For more information, please visit BugBot documentation.
Description
•