Bug 1384336 has caused a number of regressions. I think the best thing to do is to disable it for the rest of 57.

Comment on attachment 8905709 [details] [diff] [review] patch Review of attachment 8905709 [details] [diff] [review]: ----------------------------------------------------------------- Makes sense.

Pushed by wmccloskey@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/e288814a44ef Use native event processing in content process (r=mccr8)

Backed out for debug build bustage on Linux, build bustage on Windows and many test failures, especially on Android: https://hg.mozilla.org/integration/mozilla-inbound/rev/3c698f2b2eed6e29d6346c798e6234bd5b2696c4 Push with failures: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=e288814a44ef6493c8e8a30be0a3e29f3b7bfd38&filter-resultStatus=exception&filter-resultStatus=usercancel&filter-resultStatus=runnable&filter-resultStatus=retry&filter-resultStatus=testfailed&filter-resultStatus=busted Short version: Please check every test failure for that push. Longer version what can be spotted quickly: - debug build bustage on Linux - build bustage on Windows - mochitest failures on Android - assertions on OS X - timeouts in mochitests on Linux x64 opt - failure for chrome's toolkit/components/aboutmemory/tests/test_sqliteMultiReporter.xul on both Linux opts.

Pushed by wmccloskey@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/13ad384d29fb Use native event processing in content process (r=mccr8)

Bug 1426100 disabled the native event loop in content processes again.