Bug 1479251 - registeredURLs may not have been set up yet when the first process launches. r=Mossop draft
authorFelipe Gomes <felipc@gmail.com>
Tue, 31 Jul 2018 10:30:38 -0300
changeset 824636 1eb197acb4f3acddc3aaf908d617c8074130754a
parent 824607 0d72c7996d60a7c07e35c5f90d78b02a47d17460
push id117956
push userfelipc@gmail.com
push dateTue, 31 Jul 2018 13:32:50 +0000
reviewersMossop
bugs1479251
milestone63.0a1
Bug 1479251 - registeredURLs may not have been set up yet when the first process launches. r=Mossop MozReview-Commit-ID: A9kC8yJavrg
toolkit/content/process-content.js
--- a/toolkit/content/process-content.js
+++ b/toolkit/content/process-content.js
@@ -47,17 +47,17 @@ let ProcessObserver = {
       case "content-document-global-created": {
 
         // Strip the hash from the URL, because it's not part of the origin.
         let window = subject;
         let url = window.document.documentURI.replace(/[\#|\?].*$/, "");
 
         let registeredURLs = Services.cpmm.sharedData.get("RemotePageManager:urls");
 
-        if (!registeredURLs.has(url))
+        if (!registeredURLs || !registeredURLs.has(url))
           return;
 
         // Get the frame message manager for this window so we can associate this
         // page with a browser element
         let messageManager = window.QueryInterface(Ci.nsIInterfaceRequestor)
                                    .getInterface(Ci.nsIDocShell)
                                    .QueryInterface(Ci.nsIInterfaceRequestor)
                                    .getInterface(Ci.nsIContentFrameMessageManager);