loading tinderbox log causes massive memory and cpu usage
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
People
(Reporter: vlad, Unassigned)
References
Details
(Keywords: memory-footprint, perf)
Attachments
(3 files, 1 obsolete file)
Reporter | ||
Comment 3•14 years ago
|
||
Reporter | ||
Comment 4•14 years ago
|
||
Comment 5•14 years ago
|
||
Reporter | ||
Comment 6•14 years ago
|
||
Comment 8•14 years ago
|
||
Reporter | ||
Comment 9•14 years ago
|
||
Reporter | ||
Comment 10•14 years ago
|
||
Comment 11•14 years ago
|
||
Reporter | ||
Comment 12•14 years ago
|
||
Comment 13•14 years ago
|
||
Comment 14•14 years ago
|
||
Comment 15•14 years ago
|
||
Comment 16•14 years ago
|
||
Updated•13 years ago
|
Comment 17•13 years ago
|
||
Comment 18•13 years ago
|
||
Comment 20•13 years ago
|
||
Comment 22•13 years ago
|
||
Updated•10 years ago
|
Comment 24•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:jfkthame, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 25•3 years ago
|
||
Given that:
(a) a patch landed here to address CPU usage (comment 22),
(b) bug 624798 should have helped with memory usage (also see comment 22),
(c) much of the code will have changed over the past decade, and
(d) the testcase is no longer available
...I think we should close this (as "incomplete", given that we didn't apparently verify how much the above patches helped, and can no longer make meaningful comparisons).
I'm sure there are still cases where CPU and/or memory usage is significantly higher than we'd like, and it would be good to investigate them further, but let's do that by filing new bugs with relevant testcases; this specific bug is no longer usefully actionable.
Description
•