Filed by: wkocher [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=113726592&repo=autoland https://queue.taskcluster.net/v1/task/XiZ10uHhSYOD1cHVD7qAkw/runs/0/artifacts/public/logs/live_backing.log

Sounds similar to what we see on bug 1373879.

Hm, whereby this other bug was fixed. Andreas, any idea?

My guess is that we need to use some throttling like we do for WebDriver:SetWindowRect in https://searchfox.org/mozilla-central/rev/01d27fdd3946f7210da91b18fcccca01d7324fe2/testing/marionette/driver.js#1360-1409. This resize/repositioning code could probably be repurposed directly. I do find it strange that the stress test for Maximize Window that follows doesn’t exhibit the this problem, but it could be a super-rare intermittent. OrangeFactor seems to indicate it is pretty rare.

I can look into this after https://bugzilla.mozilla.org/show_bug.cgi?id=1311041, as it fits naturally on some of the new browsing context abstractions that I’m working on there. Judging by how infrequent this intermittent is, it’s probably worth waiting for.

(In reply to Andreas Tolfsen ‹:ato› from comment #4) > I do find it strange that the stress test for Maximize Window > that follows doesn’t exhibit the this problem, but it could be > a super-rare intermittent. OrangeFactor seems to indicate it is > pretty rare. And it appears it does have the same problem, as was reported in https://bugzilla.mozilla.org/show_bug.cgi?id=1380309. I’ve filed https://bugzilla.mozilla.org/show_bug.cgi?id=1381876 to ensure the Maximize Window command becomes synchronous.

This test has been rewritten and we dont support that feature anymore so closing

Moving bug to Testing::Marionette Client and Harness component per bug 1815831.