Open
Bug 1699830
Opened 3 years ago
Updated 3 years ago
Web content process consumes 2GB of memory when browsing on Facebook
Categories
(Core :: JavaScript Engine, defect, P2)
Core
JavaScript Engine
Tracking
()
REOPENED
People
(Reporter: thibaud.hauptmann, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
1.50 MB,
application/x-gzip
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
Browsing on internet
Actual results:
Firefox is using more than 4.5 Gb of ram.
Expected results:
Firefox do not use as usualy large amount of ram
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Component: Untriaged → Performance
Product: Firefox → Core
Comment hidden (obsolete) |
Comment 3•3 years ago
|
||
The Facebook web content process consumes most of the memory. Here details from the memory report:
1,834.04 MB (100.0%) -- explicit
├──1,161.61 MB (63.34%) -- window-objects
│ ├──1,109.33 MB (60.49%) -- top(https://www.facebook.com/, id=38)
│ │ ├──1,011.64 MB (55.16%) -- active
│ │ │ ├──1,010.37 MB (55.09%) -- window(https://www.facebook.com/)
│ │ │ │ ├────928.43 MB (50.62%) -- js-realm(https://www.facebook.com/)
│ │ │ │ │ ├──906.06 MB (49.40%) -- classes
│ │ │ │ │ │ ├──554.72 MB (30.25%) -- class(Object)/objects
│ │ │ │ │ │ │ ├──374.27 MB (20.41%) ── gc-heap
│ │ │ │ │ │ │ └──180.45 MB (09.84%) -- malloc-heap
│ │ │ │ │ │ │ ├──180.22 MB (09.83%) ── slots
│ │ │ │ │ │ │ └────0.23 MB (00.01%) ── elements/normal
│ │ │ │ │ │ ├──120.77 MB (06.59%) -- class(Function)/objects
│ │ │ │ │ │ │ ├──119.34 MB (06.51%) ── gc-heap
│ │ │ │ │ │ │ └────1.43 MB (00.08%) ── malloc-heap/slots
│ │ │ │ │ │ ├──114.63 MB (06.25%) -- class(Array)/objects
│ │ │ │ │ │ │ ├──112.35 MB (06.13%) ── gc-heap
│ │ │ │ │ │ │ └────2.28 MB (00.12%) ++ malloc-heap
│ │ │ │ │ │ ├───94.39 MB (05.15%) -- class(Call)/objects
│ │ │ │ │ │ │ ├──90.10 MB (04.91%) ── gc-heap
│ │ │ │ │ │ │ └───4.29 MB (00.23%) ── malloc-heap/slots
│ │ │ │ │ │ └───21.55 MB (01.17%) ++ (28 tiny)
│ │ │ │ │ └───22.37 MB (01.22%) ++ (7 tiny)
│ │ │ │ ├─────60.56 MB (03.30%) -- dom
│ │ │ │ │ ├──52.48 MB (02.86%) ── orphan-nodes
│ │ │ │ │ └───8.08 MB (00.44%) ++ (8 tiny)
│ │ │ │ ├─────21.13 MB (01.15%) ++ layout
│ │ │ │ └──────0.25 MB (00.01%) ── property-tables
│ │ │ └──────1.27 MB (00.07%) ++ (2 tiny)
│ │ └─────97.69 MB (05.33%) -- js-zone(0x1e91bb88000)
│ │ ├──54.61 MB (02.98%) ++ (14 tiny)
│ │ └──43.08 MB (02.35%) ++ strings
│ └─────52.29 MB (02.85%) -- top(none)/detached
│ ├──36.44 MB (01.99%) ++ window(https://www.facebook.com/videocall/incall/?peer_id=100002239680892)
│ └──15.85 MB (00.86%) ++ window(https://www.facebook.com/videocall/incall/?peer_id=100005678298673)
├────448.69 MB (24.46%) -- js-non-window
│ ├──377.46 MB (20.58%) -- zones
│ │ ├──342.63 MB (18.68%) -- zone(0x1e91b44b000)
│ │ │ ├──342.18 MB (18.66%) -- strings
│ │ │ │ ├──175.31 MB (09.56%) -- string(<non-notable strings>)
│ │ │ │ │ ├──158.67 MB (08.65%) -- malloc-heap
│ │ │ │ │ │ ├──158.56 MB (08.65%) ── latin1
│ │ │ │ │ │ └────0.11 MB (00.01%) ── two-byte
│ │ │ │ │ └───16.64 MB (00.91%) ++ gc-heap
│ │ │ │ └──166.88 MB (09.10%) ++ (3129 tiny)
│ │ │ └────0.45 MB (00.02%) ++ (4 tiny)
│ │ └───34.83 MB (01.90%) ++ (6 tiny)
│ ├───44.70 MB (02.44%) ++ runtime
│ ├───26.50 MB (01.44%) ++ gc-heap
│ └────0.03 MB (00.00%) ++ (2 tiny)
├────123.74 MB (06.75%) ── heap-unclassified
├─────40.20 MB (02.19%) ++ (22 tiny)
├─────36.18 MB (01.97%) -- heap-overhead
│ ├──19.76 MB (01.08%) ++ bin-unused
│ └──16.42 MB (00.90%) ++ (2 tiny)
└─────23.61 MB (01.29%) -- images
├──23.56 MB (01.28%) -- content
│ ├──22.70 MB (01.24%) -- raster/used
│ │ ├──20.21 MB (01.10%) ++ progress=10f
│ │ └───2.49 MB (00.14%) ++ (4 tiny)
│ └───0.86 MB (00.05%) ++ vector/used/progress=18f
└───0.05 MB (00.00%) ++ (2 tiny)
Andrew, do you see any obvious usage here? Maybe it's just a long-time open tab with continuous fetches of more content?
Flags: needinfo?(continuation)
Summary: RAM → Web content process consumes 2GB of memory when browsing on Facebook
Updated•3 years ago
|
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INVALID → ---
Comment 4•3 years ago
|
||
We've got a bunch of similar bugs on file for Facebook.
Component: General → JavaScript Engine
Flags: needinfo?(continuation)
Product: Invalid Bugs → Core
See Also: → 1674295
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P2
You need to log in
before you can comment on or make changes to this bug.
Description
•