Open
Bug 1759827
Opened 3 years ago
Updated 2 years ago
Investigate memory usage behavior while running the matrix-react benchmark
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: jandem, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
I'm attaching a modified version of the matrix-react benchmark. It does 2000 iterations instead of the usual 200.
In Chrome, the content process has stable memory usage while running the benchmark, but in Firefox we allocate more and more memory and release it after the benchmark has finished. It would be good to understand what's happening there.
|
||
Comment 1•2 years ago
|
||
Not intended to land.
This allocates the DOM nodes used by the matrix react benchmark in the nursery.
|
Reporter | |
Updated•2 years ago
|
Flags: needinfo?(jdemooij)
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•