1254926 - [e10s-multi] lots of test failing with NS_ERROR_NOT_INITIALIZED during hide popup

Status: RESOLVED FIXED

(Core :: DOM: Editor, defect)

Description

[Gabor Krizsanits (INACTIVE)]

With multiple content processes enabled, lots of tests failing with:

uncaught exception - NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMessageSender.sendAsyncMessage] at resource://gre/modules/InlineSpellChecker.jsm:592 many tests

It seems like remote spell checker is not really multiple content process compatible.

Comment 1

[Gabor Krizsanits (INACTIVE)]

https://treeherder.mozilla.org/logviewer.html#?job_id=17716701&repo=try

example stack:

 09:16:22     INFO -  776 INFO TEST-PASS | browser/base/content/test/general/browser_bug424101.js | context menu behavior for <input type=submit > is wrong -
 09:16:22     INFO -  Not taking screenshot here: see the one that was previously logged
 09:16:22     INFO -  777 INFO TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_bug424101.js | uncaught exception - NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMessageSender.sendAsyncMessage] at resource://gre/modules/InlineSpellChecker.jsm:592
 09:16:22     INFO -  Stack trace:
 09:16:22     INFO -      chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:simpletestOnerror:1543
 09:16:22     INFO -      chrome://global/content/bindings/popup.xml:hidePopup:134
 09:16:22     INFO -      chrome://mochitests/content/browser/browser/base/content/test/general/browser_bug424101.js:null:47
 09:16:22     INFO -      Tester_execTest@chrome://mochikit/content/browser-test.js:790:9
 09:16:22     INFO -      Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:710:7
09:16:22 INFO - SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:741:59

Comment 2

[Gabor Krizsanits (INACTIVE)]

Attachment: fix browser_addKeywordSearch test

This is the first test that fails in the suit because a trivial bug in the test and a tab stays open because of it... Let's see if it fixes the rest of the failures in the suite.

Comment 3

[Blake Kaplan (:mrbkap) (inactive)]

Comment on attachment 8775956 [details] [diff] [review]
fix browser_addKeywordSearch test

Review of attachment 8775956 [details] [diff] [review]:
-----------------------------------------------------------------

::: browser/base/content/test/general/browser_addKeywordSearch.js
@@ +20,5 @@
>        let base = doc.createElement("base");
>        doc.head.appendChild(base);
>      });
>  
> +    var mm = gBrowser.selectedBrowser.messageManager;

Just use the parameter |browser| which has been passed in already.

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f14ceb85c47d
Fixing addKeywordSearch test for e10s-multi. r=mrbkap

Comment 5

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/f14ceb85c47d