1366020 - [nsIStreamListener.onStartRequest] WebRequest.jsm:340 error

Status: RESOLVED WONTFIX

(WebExtensions :: Request Handling, defect)

Description

[Jonathan Kingston [:jkt] he/him]

I am seeing the following in my browser console for our test pilot.

NS_BINDING_ABORTED: Component returned failure code: 0x804b0002 (NS_BINDING_ABORTED) [nsIStreamListener.onStartRequest]  WebRequest.jsm:340

We also have an onCompleted webRequest handler too but I suspect it is the above.

I only start to see this error when {cancel: true} is active for the website.

STR:
1. (using test pilot extension)
2. Open browser console and filter by "WebRequest"
3. Leave a about:newtab page open
4. Open google tab in work
5. Switch between a new tab and work

At step 4. I get the error randomly appearing, it doesn't seem related to any of the code we have... I think.


If it is, it will likely be this method:

    browser.webRequest.onBeforeRequest.addListener((options) => {
      if (options.frameId !== 0 || options.tabId === -1) {
        return {};
      }
      return Promise.all([
        browser.tabs.get(options.tabId),
        this.storageArea.get(options.url)
      ]).then(([tab, siteSettings]) => {
        const userContextId = this.getUserContextIdFromCookieStore(tab);
        if (!siteSettings
            || userContextId === siteSettings.userContextId
            || tab.incognito) {
          return {};
        }
        // More code here...
      }).catch((e) => {
        throw e;
      });
    },{urls: ["<all_urls>"], types: ["main_frame"]}, ["blocking"]);


This may be a dupe of Bug 1333141

Comment 1

[Kris Maglione [:kmag]]

This is an unfortunate side-effect of the way XPConnect error reporting happens, but we can't do anything about it. This error is from the original stream listener that we're wrapping, but when we propagate it up the chain, it gets reported as it crosses an XPConnect boundary.

Comment 2

[Jonathan Kingston [:jkt] he/him]

Ah, thanks for the explanation all the same!