Filed by: bclary [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=125740119&repo=autoland https://autophone.s3.amazonaws.com/v1/task/BmjkypOlRTOUYKxKCdgp3w/runs/0/artifacts/public/build/6654803c-151a-4219-add0-fe55631817bd-autophone.log

Since its failure rate is super low, I think it's not worth to spend time investigating it. I'll prefer to wait for a long while to see its trend (still happen or disappear).

alwu: I've re-enabled Mdm1 and at first glance this appears to be happening on Android 4.4. If it turns out to be common on 4.4, I'll disable it. https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=autophone&fromchange=fa0f66eaa81fa9663de8e1d73f1299c585ef53f8&group_state=expanded&selectedJob=142439079

I'm not working on Fennec test case now, transfer NI to John.

Pushed by bclary@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/006b8806bac9 disable dom/media/test/test_resolution_change.html on Android 4.4 due to time outs, r=gbrown.

The log shows media shutdown process timed out, just like bug 1392747: 11-20 15:30:25.872 I/Gecko ( 6404): FATAL ERROR: AsyncShutdown timeout in profile-before-change Conditions: [{"name":"MediaShutdownManager: shutdown","state":"(none)","filename":"/builds/worker/workspace/build/src/dom/media/MediaShutdownManager.cpp","lineNumber":83,"stack":"MediaShutdownManager shutdown"}] At least one completion condition failed to complete within a reasonable amount of time. Causing a crash to ensure that we do not leave the user with an unresponsive process draining resources.