1447807 - Error: browser.ownerGlobal is null

Status: VERIFIED FIXED

(WebExtensions :: Request Handling, defect, P2)

Description

[Kris Maglione [:kmag]]

This bug was automatically filed from Sentry: https://sentry.prod.mozaws.net/operations/nightly-js-errors/issues/3169594/

Error: browser.ownerGlobal is null
    at getBrowserData(chrome://browser/content/ext-browser.js:546:9)
    at listener(chrome://extensions/content/ext-webRequest.js:22:23)
    at runChannelListener/<(resource://gre/modules/WebRequest.jsm:773:24)
    at forEach(self-hosted:3625:9)
    at runChannelListener(resource://gre/modules/WebRequest.jsm:739:7)
    at handleEvent(resource://gre/modules/WebRequest.jsm:711:9)

Comment 1

[Trishul]

STR:

• install https-everywhere
• open private window
• open 3-4 tabs with search queries(do not complete address, let search engine load results)
• close the private window
• error can be seen in console

I believe we can subside the error here
https://searchfox.org/mozilla-central/source/toolkit/components/extensions/parent/ext-webRequest.js#29
with
if (data.browser && data.browser.ownerGlobal) {

Comment 2

[Shane Caraveo (:mixedpuppy)]

I'd rather see it fixed inside tabTracker.getBrowserData.

https://searchfox.org/mozilla-central/rev/088e2cf29c59d733d57af43903eb0267dbf72e2a/browser/components/extensions/parent/ext-browser.js#701

Probably doing something like:

https://searchfox.org/mozilla-central/rev/088e2cf29c59d733d57af43903eb0267dbf72e2a/mobile/android/components/extensions/ext-utils.js#336

Comment 3

[Trishul]

Sounds good, I will create a patch

Comment 4

[Trishul]

Attachment: Bug 1447807 - Error: browser.ownerGlobal is null

Error: browser.ownerGlobal is null

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/652978346e60
Error: browser.ownerGlobal is null r=mixedpuppy

Comment 6

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/652978346e60

Comment 7

[Alex Cornestean]

Hello,

Verified the fix using the latest Nightly (72.0a1/20191027212548) under Windows 10 Pro 64-bit and MacOS Catalina 10.15.

Proceeding with the STR from Comment 1 will no longer produce the error.