High frequency Linux/Windows browser/base/content/test/performance/browser_tabopen.js | unexpected changed rect: ({x1:213, x2:230, y1:4, y2:39, w:18, h:36}), window width: 1280 -
Categories
(Firefox :: General, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox96 | --- | unaffected |
firefox97 | --- | unaffected |
firefox98 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: emilio)
References
(Regression)
Details
(Keywords: intermittent-failure, regression, Whiteboard: [stockwell disable-recommended])
Attachments
(6 files, 1 obsolete file)
Filed by: smolnar [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=365236037&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/J1fbjOsJTwaztdgAayNBCg/runs/0/artifacts/public/logs/live_backing.log
INFO - TEST-PASS | browser/base/content/test/performance/browser_tabopen.js | 0 unexpected reflows - true == true -
[task 2022-01-24T14:39:13.052Z] 14:39:13 INFO - comparing 4 frames
[task 2022-01-24T14:39:13.053Z] 14:39:13 INFO - Buffered messages finished
[task 2022-01-24T14:39:13.054Z] 14:39:13 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_tabopen.js | unexpected changed rect: ({x1:213, x2:230, y1:4, y2:39, w:18, h:36}), window width: 1280 -
[task 2022-01-24T14:39:13.054Z] 14:39:13 INFO - Stack trace:
[task 2022-01-24T14:39:13.056Z] 14:39:13 INFO - chrome://mochikit/content/browser-test.js:test_ok:1375
[task 2022-01-24T14:39:13.057Z] 14:39:13 INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:reportUnexpectedFlicker/rects<:633
[task 2022-01-24T14:39:13.058Z] 14:39:13 INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:reportUnexpectedFlicker:624
[task 2022-01-24T14:39:13.059Z] 14:39:13 INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:withPerfObserver:693
INFO - data:image/png;base64
INFO - data:image/png;base64
INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-01-24T14:39:13.238Z] 14:39:13 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_tabopen.js | should have 0 unknown flickering areas - Got 1, expected +0
[task 2022-01-24T14:39:13.239Z] 14:39:13 INFO - Stack trace:
[task 2022-01-24T14:39:13.240Z] 14:39:13 INFO - chrome://mochikit/content/browser-test.js:test_is:1403
[task 2022-01-24T14:39:13.241Z] 14:39:13 INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:reportUnexpectedFlicker:650
[task 2022-01-24T14:39:13.242Z] 14:39:13 INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:withPerfObserver:693
[task 2022-01-24T14:39:13.242Z] 14:39:13 INFO - Leaving test bound
[task 2022-01-24T14:39:13.243Z] 14:39:13 INFO - GECKO(4279) | MEMORY STAT | vsize 20984129MB | residentFast 1888MB
[task 2022-01-24T14:39:13.244Z] 14:39:13 INFO - TEST-OK | browser/base/content/test/performance/browser_tabopen.js | took 1491ms
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Dao, do you know how to best deal with this? This is not totally unexpected, and before it was happening just racily because of the delay in setting visibility... Should I just whitelist the rect?
Comment 2•3 years ago
|
||
So this is from browser_tabopen.js
's usage of withPerfObserver
which takes an allowed list of differing-rects and complains if there are changes that don't match that list.
The data URI screenshots show Firefox...
(1) just as the new tab is starting to appear (its "x" is barely visible, nothing else)
(2) after the new tab has finished opening.
This seems fine. The differences between the two are entirely contained in the tab-strip (in the area that the new tab occupies).
And browser_tabopen.js
seems to intend to allow differences there, per its comment // We expect all changes to be within the tab strip
.
So: seems like we likely need to adjust/add to the allowed-rect-list here.
Comment 3•3 years ago
|
||
Comment 4•3 years ago
|
||
Comment 5•3 years ago
|
||
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 6•3 years ago
|
||
Updated•3 years ago
|
Assignee | ||
Comment 7•3 years ago
|
||
From looking at the screenshot I think this should do, but lmk if you
think otherwise or I got the wrong padding here... Also dump more
information for the next time the test fails.
Depends on D136783
Assignee | ||
Comment 8•3 years ago
|
||
Comment 10•3 years ago
|
||
Emilio, the changes didn`t fix the failure.
The failure rate it is still high -> https://treeherder.mozilla.org/jobs?repo=autoland&selectedTaskRun=X8OqIXoXSce7n2fLFcLQFw.0&resultStatus=success%2Ctestfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=393e2d7c6bd57457f2d1f9981151e8c46296a8ca&searchStr=linux%2C18.04%2Cx64%2Cwebrender%2Casan%2Copt%2Cmochitests%2Cwith%2Csoftware%2Cwebrender%2Cand%2Cfission%2Cenabled%2Ctest-linux1804-64-asan-qr%2Fopt-mochitest-browser-chrome-swr-fis-e10s%2Cbc4
Assignee | ||
Comment 11•3 years ago
|
||
Yes, that's expected, see the other two patches.
Comment 12•3 years ago
|
||
Note (given that the fixes are pending review): if the failure rate is painfully high and is a burden on sheriffs, I think it'd be fine to backout bug 1751484 for now (which should stop the failures), and we can re-land that bug's patch once we've got a full stack of r+'d patches here.
Comment hidden (Intermittent Failures Robot) |
Comment 14•3 years ago
|
||
This happens on windows too: https://treeherder.mozilla.org/logviewer?job_id=365321255&repo=autoland
Comment 15•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Updated•3 years ago
|
Comment 16•3 years ago
|
||
Recent failures have been fixed by backout: https://hg.mozilla.org/integration/autoland/rev/302ff8c8329a7fcf31571b700e62873512a679d4
Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
Updated•3 years ago
|
Comment 18•3 years ago
|
||
Comment 19•3 years ago
|
||
bugherder |
Assignee | ||
Comment 20•3 years ago
|
||
Whether the overflow happens intentionally or not, it wasn't caused by
the regressing patch so I think we should probably just do this for now.
Comment 21•3 years ago
|
||
Updated•3 years ago
|
Comment 22•3 years ago
|
||
bugherder |
Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment hidden (Intermittent Failures Robot) |
Description
•