So there are two failures: ``` Unexpected modules loaded during content process startup: resource://gre/modules/ComponentUtils.jsm Unexpected modules loaded during content process startup: chrome://marionette/content/prefs.js ``` So the [changes to dom/security/nsContentSecurityManager.cpp](https://hg.mozilla.org/integration/autoland/rev/270e0f9613a6) were causing that. Given that this code runs within a content process, getting the Marionette service and it's `running` property seems to cause a [MarionetteContentProcess](https://searchfox.org/mozilla-central/rev/be906232eedb22c064b78f3806b38964c04f1fbc/testing/marionette/components/marionette.js#568-573) to be created. But that is interesting because we have the instance check and Marionette should Given that `ComponentUtils` and both imports from `prefs.js` aren't lazily loaded, we see the above two failures.
Bug 1699627 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
So there are two failures: ``` Unexpected modules loaded during content process startup: resource://gre/modules/ComponentUtils.jsm Unexpected modules loaded during content process startup: chrome://marionette/content/prefs.js ``` The [changes to dom/security/nsContentSecurityManager.cpp](https://hg.mozilla.org/integration/autoland/rev/270e0f9613a6) were causing that. Given that this code runs within a content process, getting the Marionette service and it's `running` property causes the [marionette.js](https://searchfox.org/mozilla-central/rev/be906232eedb22c064b78f3806b38964c04f1fbc/testing/marionette/components/marionette.js) module loaded in the content process. Given that `ComponentUtils` and both imports from `prefs.js` aren't lazily loaded, we see the above two failures.