Treeherder consuming much memory/RAM (and CPU due to GC/garbage collection?)
Categories
(Tree Management :: Treeherder: Frontend, defect, P1)
Tracking
(Not tracked)
People
(Reporter: aryx, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
Attachments
(2 files)
Reporter | ||
Comment 2•6 years ago
|
||
Updated•6 years ago
|
Reporter | ||
Comment 3•6 years ago
|
||
Comment 4•6 years ago
|
||
Updated•6 years ago
|
Comment 5•6 years ago
|
||
Comment 6•6 years ago
|
||
Comment 7•6 years ago
|
||
Reporter | ||
Comment 8•6 years ago
|
||
Comment 9•6 years ago
|
||
Reporter | ||
Comment 10•6 years ago
|
||
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
Comment 16•6 years ago
|
||
Comment 17•6 years ago
|
||
Comment 18•6 years ago
|
||
Updated•6 years ago
|
Comment 20•6 years ago
|
||
Comment 21•6 years ago
|
||
Comment 22•6 years ago
|
||
Updated•6 years ago
|
Comment 23•6 years ago
|
||
Is this issue still occurring?
Comment 24•6 years ago
|
||
I can't say for sure if it's the same issue, but today I had to kill a content process because treeherder was making it unresponsive. I could capture a profile before killing it: https://perfht.ml/2Dg28x9
Comment 25•6 years ago
|
||
Ah that's good to know - and thank you for the profile.
Cameron, did you have any more ideas for this bug? :-)
Comment 26•6 years ago
|
||
Another profile captured today: https://perfht.ml/2JyXpNu
Comment 27•5 years ago
|
||
Leaving treeherder open in a background tab still makes the content process unusable: https://perfht.ml/2DUhWHe
Comment 28•5 years ago
|
||
I believe this is now remedied. I haven't heard complaints about memory consumption in a while. And, while Treeherder requires quite a bit of memory, it does not appear to grow unbounded any longer.
Please reopen if you run into more issues in this regard.
Comment 29•4 years ago
|
||
I forgot a treeherder tab in the background again, and that made the content process unresponsive (and it used about 6GB of memory) Here's a profile of it, that made me identify the treeherder tab as the culprit: https://share.firefox.dev/2Tqpx7R
This looks pretty similar to the profile I had in comment 27; reopening.
Comment 30•4 years ago
|
||
I am in a sprint and can't tackle this any time soon till it is in a Sprint. Removing myself.
Description
•