e10s compatibility for Torbutton's content sizer
Torbutton will need to be revised in various ways for compatiblity with Firefox's multiprocess mode (aka electrolysis or e10s). One example is the content sizer code. Here is the first error that Kathy and I saw:
A coding exception was thrown and uncaught in a Task.
Full message: TypeError: gBrowser.contentWindow is null
Full stack: quantizeBrowserSize/updateDimensions@chrome://torbutton/content/content-sizer.js:247:18
quantizeBrowserSize/autoresize/<@chrome://torbutton/content/content-sizer.js:436:7
TaskImpl_run@re[/gre/modules/Task.jsm:319:42](/gre/modules/Task.jsm:319:42)
TaskImpl@re[/gre/modules/Task.jsm:277:3](/gre/modules/Task.jsm:277:3)
createAsyncFunction/asyncFunction@re[/gre/modules/Task.jsm:252:14](/gre/modules/Task.jsm:252:14)
Task_spawn@re[/gre/modules/Task.jsm:166:12](/gre/modules/Task.jsm:166:12)
quantizeBrowserSize/autoresize@chrome://torbutton/content/content-sizer.js:431:3
quantizeBrowserSize/quantizeBrowserSizeMain/activate@chrome://torbutton/content/content-sizer.js:487:30
bindPref/update@re[/torbutton/modules/utils.js:31:24](/torbutton/modules/utils.js:31:24)
bindPref@re[/torbutton/modules/utils.js:39:5](/torbutton/modules/utils.js:39:5)
bindPrefAndInit@re[/torbutton/modules/utils.js:49:5](/torbutton/modules/utils.js:49:5)
quantizeBrowserSize/quantizeBrowserSizeMain@chrome://torbutton/content/content-sizer.js:501:16
quantizeBrowserSize/stopObserving<@chrome://torbutton/content/content-sizer.js:508:5
observe/observer.observe@re[/torbutton/modules/utils.js:61:9](/torbutton/modules/utils.js:61:9)
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information