Closed Bug 1397268 Opened 7 years ago Closed 7 years ago

Intermittent TEST-UNEXPECTED-FAIL | leakcheck | tab process: missing output line for total leaks!

Categories

(Core :: Gecko Profiler, defect, P5)

Product:
Core
Component:
Gecko Profiler
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1368036

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Whiteboard: [stockwell unknown])

There were 38 failures related to this bug in the last 7 days. This occurs on Linux 64 debug reftest. Here is an example of the log: https://treeherder.mozilla.org/logviewer.html#?repo=mozilla-inbound&job_id=142603878&lineNumber=1900 I noticed that the reftest analyzer is not loading accordingly because of the crashes: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/Z6TjG08mSRWOt_1LvL-wCw/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1 :mstange can you take a look at this?
Flags: needinfo?(mstange)
Whiteboard: [stockwell needswork]
(In reply to Andrei Ciure[:andrei_ciure_] from comment #9) > There were 38 failures related to this bug in the last 7 days. This occurs > on Linux 64 debug reftest. The more frequent recent failures are new and are caused by something different than the failure that this bug was originally filed about. The new failures all contain the line Assertion failure: mKnowsCompositor->GetCompositorBackendType() == LayersBackend::LAYERS_CLIENT In particular, you can see here: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&tochange=0418d4d4a91ef989fb18d56a1b30e2a6e413cec5&fromchange=ffd4e32a403a933d53a1aa84edf94aa4b7a76dfc&filter-searchStr=Linux%20debug that these failures started with the landing of bug 1411472, which has been backed out again because of those failures.
Flags: needinfo?(mstange)
See Also: → 1395910
It was originally about a hang in a reftest: we have repeatedly demonstrated that we cannot have an open bug suggested about this particular line of output, because we will ignore the fact that it is present every single time we crash on debug in any way, and we will just pile every random crash onto it.
Status: NEW → RESOLVED
Closed: 7 years ago
Keywords: intermittent-failure
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.