Open Bug 1628960 Opened 5 years ago Updated 3 days ago

Intermittent TEST-UNEXPECTED-FAIL | leakcheck | gpu missing output line for total leaks!

Categories

(Core :: DOM: Content Processes, defect, P3)

defect

Tracking

()

REOPENED

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: intermittent-failure, regression, Whiteboard: [retriggered][stockwell unknown])

Filed by: rmaries [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=297096454&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Ht03nVgiQZ6BCXugTaYqDA/runs/0/artifacts/public/logs/live_backing.log


[task 2020-04-10T04:23:04.343Z] 04:23:04 INFO - TEST-START | /dom/ranges/StaticRange-constructor.html
[task 2020-04-10T04:23:27.589Z] 04:23:27 INFO - TEST-INFO | leakcheck | tab ignoring missing output line for total leaks
[task 2020-04-10T04:23:27.590Z] 04:23:27 INFO - leakcheck | Processing leak log file /tmp/tmpTRhMNH/runtests_leaks_980_gpu_pid10253.log
[task 2020-04-10T04:23:27.590Z] 04:23:27 INFO - TEST-UNEXPECTED-FAIL | leakcheck | gpu missing output line for total leaks!
[task 2020-04-10T04:23:27.591Z] 04:23:27 INFO - leakcheck | Processing leak log file /tmp/tmpTRhMNH/runtests_leaks_980.log

This looks to be regressed by the same bug that caused a spike of failures in Bug 1535922, meaning Bug 1626089 which has a fix landed.

See Also: → 1535922, 1626089
Regressed by: 1626089
Whiteboard: [stockwell needswork:owner] → [stockwell needswork:owner][retriggered]
Has Regression Range: --- → yes
Priority: -- → P3

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---

This error means the GPU process is exiting for some reason before we record the shutdown leak log, so this bug should live in Core: Graphics. The concern here is that if we are never recording a leak log, then we can't find leaks. This isn't a big deal as long as the failure rate is low, as it is.

Component: DOM: Core & HTML → Graphics

I went and looked at the last 5 or so failures, and it looks like a bunch of process types aren't recording leak logs, so this isn't actually specific to graphics. Maybe we should report a different error for that so that we can find out if the GPU process specifically has leak issues. This should probably be in Content Processes or maybe IPC. This looks to be a problem specifically with web-platform-tests-wdspec-1.

Component: Graphics → DOM: Content Processes
You need to log in before you can comment on or make changes to this bug.