Closed Bug 1103109 Opened 10 years ago Closed 9 years ago

mozmill-2.0 causes 10-20MB regression in AWSY

Categories

(Testing Graveyard :: Mozmill, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: erahm, Unassigned)

References

(Blocks 1 open bug)

Details

When attempting to switch AWSY to mozmill-2.0 we noticed a 10-20MB regression in memory usage after running TP5. This prevented us from switching to 2.0. Unfortunately it looks like we've rerun all of the 2.0 entries so I don't have concrete numbers.

STR are essentially:
- Open 30 tabs to different sites
- Cycle through them and navigate to a new site in each, do this 3 times
- Close all tabs (point last one to about:blank)
- Measure memory usage after tabs are closed

Expected: memory usage would be the same b/w 1.5 and 2.0
Eric, do you have a leak log for that? It would be great if you could attach one to this bug, so that we can see what exactly is leaking. If you would have a minimized mozmill test, even better.
Flags: needinfo?(erahm)
I don't have leak logs. Reducing a test is probably beyond my expertise level w/ mozmill, but you can take a look at the test [1] if my STR wasn't clear enough.

[1] https://github.com/mozilla/areweslimyet/blob/master/mozmill_endurance_test/test1.js
Flags: needinfo?(erahm)
Blocks: AWSY
We would need someone to get this investigated. We wont have the time for that. Eric, given that you are working on a Marionette solution, I assume its no longer a blocker for you. In that case I would vote for wontfixing this bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.