Memory increase in backgrounded (paused) twitch.tv tab
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: metasieben, Unassigned)
Details
Attachments
(1 file)
|
538.41 KB,
application/x-gzip
|
Details |
While trying to recreate bug 1772806, I saved a memory report of the browser with the twitch tab using more than 1GB.
The tab was in the background and stopped, the computer(Mac mini M1, 8GB) was locked.
Here a profile created in about:processes: https://share.firefox.dev/3HkgvRD
Comment 1•4 years ago
|
||
Wow, I've never seen so much storage for WeakMaps.
webIsolated=https://twitch.tv (pid 61798)
Explicit Allocations
1,300.09 MB (100.0%) -- explicit
├──1,034.13 MB (79.54%) -- window-objects/top(https://www.twitch.tv/videos/1486195733, id=288)
│ ├────932.67 MB (71.74%) -- active/window(https://www.twitch.tv/videos/1486195733)
│ │ ├──890.98 MB (68.53%) -- js-realm(https://www.twitch.tv/videos/1486195733)
│ │ │ ├──877.23 MB (67.47%) -- classes
│ │ │ │ ├──302.32 MB (23.25%) -- class(Object)/objects
│ │ │ │ │ ├──218.31 MB (16.79%) ── gc-heap
│ │ │ │ │ └───84.01 MB (06.46%) -- malloc-heap
│ │ │ │ │ ├──83.95 MB (06.46%) ── slots
│ │ │ │ │ └───0.06 MB (00.00%) ── elements/normal
│ │ │ │ ├──159.96 MB (12.30%) -- class(Set)/objects
│ │ │ │ │ ├──125.65 MB (09.66%) ── malloc-heap/misc
│ │ │ │ │ └───34.31 MB (02.64%) ── gc-heap
│ │ │ │ ├──123.52 MB (09.50%) -- class(WeakMap)/objects
│ │ │ │ │ ├──119.46 MB (09.19%) ── malloc-heap/misc
│ │ │ │ │ └────4.06 MB (00.31%) ── gc-heap
│ │ │ │ ├──105.75 MB (08.13%) -- class(Map)/objects
│ │ │ │ │ ├───86.96 MB (06.69%) ── malloc-heap/misc
│ │ │ │ │ └───18.79 MB (01.45%) ── gc-heap
I suspect the page is leaking, for some definition of "leaking". Would you happen to know if it exhibits similar behavior on another browser?
It looks like we have a whole meta bug on problems with Twitch on Firefox vs. Chrome. I don't know whether this bug should be on that list or not.
Comment 2•4 years ago
|
||
The severity field is not set for this bug.
:glandium, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 3•2 years ago
|
||
I'll assume this has disappeared in the past two years, but if it hasn't please feel free to reopen with an up-to-date report.
Description
•