1628075 - Intermittent editor/libeditor/crashtests/1424450.html | load failed: timed out waiting for pending paint count to reach zero (waiting for updateCanvasPending)

Status: RESOLVED DUPLICATE of bug 1635914

(GeckoView :: General, defect, P1)

Description

[Treeherder Bug Filer]

Filed by: rmaries [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=296654616&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/E_-td_TdQUKvJhvSWdpZRA/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/E_-td_TdQUKvJhvSWdpZRA/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---

Comment 1

[Intermittent Failures Robot]

22 failures in 4823 pushes (0.005 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 14
• mozilla-central: 4
• try: 4

Platform breakdown:

• android-hw-p2-8-0-android-aarch64-qr: 22

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1628075&startday=2020-04-06&endday=2020-04-12&tree=all

Comment 2

[Natalia Csoregi [:nataliaCs]]

Retriggered/backfilled: https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&searchStr=android%2C8.0%2Cpixel2%2Caarch64%2Cquantumrender%2Cdebug%2Creftests%2Ctest-android-hw-p2-8-0-android-aarch64-qr%2Fdebug-geckoview-crashtest-e10s%2Cr%28c%29&tochange=31efa8051c3a4b54c07bfa361784d274c8dc847f&fromchange=67ed70a179f29c358c5c0e10310ca38dd48d70c8&selectedJob=297369403

Could it be caused by https://hg.mozilla.org/integration/autoland/rev/406e5dda843f367da8d91a55aabde132da5a3188 ?
Thank you.

Comment 3

[(No longer employed by Mozilla) Aaron Klotz]

It's "caused" in the sense that now we're seeing it, but backing out is not the fix for this. I think we might need to make some changes in the test harness. I'll look into this.

The issue is that, now that we support process prioritization, the current content process does not have focus, and thus is a lesser priority than the parent process. We might need to disable prioritization while running this harness.

Comment 4

[Intermittent Failures Robot]

29 failures in 4528 pushes (0.006 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 22
• mozilla-central: 6
• try: 1

Platform breakdown:

• android-hw-p2-8-0-android-aarch64-qr: 29

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1628075&startday=2020-04-13&endday=2020-04-19&tree=all

Comment 5

[(No longer employed by Mozilla) Aaron Klotz]

Our test activity is prioritizing content processes differently than GVE such that the content process in the reftest is never bumped up to high priority. I suspect that the timeout is simply because the content process isn't getting enough CPU time to complete quickly enough.

Moving to GeckoView since it's our test activity that needs to be fixed, not reftest.

Comment 6

[Intermittent Failures Robot]

15 failures in 5582 pushes (0.003 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 12
• try: 1
• mozilla-central: 2

Platform breakdown:

• android-hw-p2-8-0-android-aarch64-qr: 15

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1628075&startday=2020-04-20&endday=2020-04-26&tree=all

Comment 7

[(No longer employed by Mozilla) Aaron Klotz]

Attachment: Bug 1628075: Ensure that the active session is set to active, since the test activity might not be visible; r=#geckoview-reviewers

If the session is not perceived as active, then Gecko will not boost the
session's hosting content process to FOREGROUND priority.

Comment 8

[(No longer employed by Mozilla) Aaron Klotz]

This was fixed by bug 1635914.