Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Unified Diff: lib/main.js

Issue 29329895: Issue 3290 - Adblock Plus child modules don`t always start up (Closed)
Patch Set: Created Nov. 9, 2015, 3:37 p.m.
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« lib/child/bootstrap.js ('K') | « lib/child/bootstrap.js ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: lib/main.js
===================================================================
--- a/lib/main.js
+++ b/lib/main.js
@@ -31,23 +31,24 @@ require("notification");
require("sync");
require("messageResponder");
require("ui");
require("objectTabs");
function bootstrapChildProcesses()
{
let info = require("info");
+ let {Utils} = require("utils");
+ Utils.addChildMessageListener("AdblockPlus:GetInfo", () => info);
let processScript = info.addonRoot + "lib/child/bootstrap.js?" + Math.random();
let messageManager = Cc["@mozilla.org/parentprocessmessagemanager;1"]
.getService(Ci.nsIProcessScriptLoader)
.QueryInterface(Ci.nsIMessageBroadcaster);
messageManager.loadProcessScript(processScript, true);
- messageManager.broadcastAsyncMessage("AdblockPlus:Info", info);
onShutdown.add(() => {
messageManager.broadcastAsyncMessage("AdblockPlus:Shutdown", processScript);
messageManager.removeDelayedProcessScript(processScript);
});
}
function registerPublicAPI()
« lib/child/bootstrap.js ('K') | « lib/child/bootstrap.js ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld