Closed
Bug 669322
Opened 13 years ago
Closed 13 years ago
Add an endurance test for memory use after closing a bunch of tabs
Categories
(Testing :: Talos, defect)
Testing
Talos
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 669613
People
(Reporter: khuey, Unassigned)
References
Details
(Whiteboard: [MemShrink:P1])
One of the "metrics" of Firefox memory usage is "close a bunch of tabs and see how much memory usage goes down". We should be measuring this as part of Talos.
Updated•13 years ago
|
Whiteboard: [MemShrink]
Updated•13 years ago
|
Version: unspecified → Trunk
Comment 1•13 years ago
|
||
Talos (Tp) currently doesn't open a lot of tabs at once. So let's make this an endurance test instead. (Or did we specifically want to use the Talos page set?)
Summary: Add a Talos measurement for memory in use after closing lots of tabs. → Add an endurance test for memory use after closing a bunch of tabs
Whiteboard: [MemShrink] → [MemShrink:P1]
Reporter | ||
Comment 2•13 years ago
|
||
The particular pageset used doesn't really matter to me as long as it's representative of the web.
Of course, it seems like a good idea to curate as few pagesets as possible ...
Comment 3•13 years ago
|
||
I had bits and pieces of a test that would open each page of tp into a separate tab and then close them - is that the sort of thing that you are looking for?
I believe that the missing components would be in determining the memory footprint change over the course of the test.
Comment 4•13 years ago
|
||
This would be covered by the 'membuster' endurance test. See bug 669613.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•