Closed Bug 1717641 Opened 3 years ago Closed 3 years ago

Error: Please use $(ref:runtime.getURL) - getExtensionInfo - and others

Categories

(WebExtensions :: Request Handling, defect)

Firefox 91
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1712335

People

(Reporter: wtds.trabalho, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

  • Firefox Nightly
  • Daily use
  • Common messages or warning in browser console
  • Sometime errors
  • Maybe related to addons, but in browser JS dependencies. Deprecation?

Actual results:

The errors:

Error: Please use $(ref:runtime.getURL). backgroundLogic.js:25
    getExtensionInfo moz-extension://217edf57-d707-468e-b6b8-90fe450dc96c/js/background/backgroundLogic.js:25
Error: Please use $(ref:runtime.getURL).
NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIDocShell.domWindow]
NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIDocShell.domWindow] browsing-context.js:409
    get window resource://devtools/server/actors/targets/browsing-context.js:409
    _onDocShellDestroy resource://devtools/server/actors/targets/browsing-context.js:897
    observe resource://devtools/server/actors/targets/browsing-context.js:835
Exception { name: "NS_ERROR_NOT_AVAILABLE", message: "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannelInternal.remoteAddress]", result: 2147746065, filename: "resource://devtools/server/actors/network-monitor/network-observer.js", lineNumber: 1043, columnNumber: 0, data: null, stack: "_onResponseHeader@resource://devtools/server/actors/network-monitor/network-observer.js:1043:5\n_dispatchActivity@resource://devtools/server/actors/network-monitor/network-observer.js:620:14\nNetworkObserver.prototype.observeActivity<@resource://devtools/server/actors/network-monitor/network-observer.js:729:12\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:103:22\n", location: XPCWrappedNative_NoHelper }
ThreadSafeDevToolsUtils.js:82:13
    reportException resource://devtools/shared/ThreadSafeDevToolsUtils.js:82
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:109
Security Error: Content at moz-nullprincipal:{45de8e0f-3804-41c4-aeeb-f8f9c0af68fd} may not load or link to resource://devtools/shared/ThreadSafeDevToolsUtils.js.
<Provider> does not support changing `store` on the fly. It is most likely that you see this error because you updated to Redux 2.x and React Redux 2.x which no longer hot reload reducers automatically. See https://github.com/reactjs/react-redux/releases/tag/v2.0.0 for the migration instructions. react-redux.js:881:13
    Redux 3
        warning$2
        warnAboutReceivingStore
        componentWillReceiveProps
    React 38
    renderApp resource://devtools/client/webconsole/webconsole-wrapper.js:41
    init resource://devtools/client/webconsole/webconsole-wrapper.js:121
    init resource://devtools/client/webconsole/webconsole-wrapper.js:85
    _initializer resource://devtools/client/webconsole/webconsole-ui.js:163
[Exception... "Favicon at "https://devnull.perfops.net/favicon.ico" failed to load: Not Found."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 253"  data: no] FaviconLoader.jsm:253:22
    onStopRequest resource:///modules/FaviconLoader.jsm:253
resource://devtools/server/actors/targets/browsing-context.js
  /**
   * Getter for the browsing context's current DOM window.
   */
  get window() {
    return this.docShell && this.docShell.domWindow;
  },
    return this.docShell && this.docShell.domWindow;
debuggee 'resource://devtools/shared/base-loader.js:289' would run
view-source:resource://devtools/client/shared/vendor/react-redux.js
  warning$2('<Provider> does not support changing `store` on the fly. ' + 'It is most likely that you see this error because you updated to ' + 'Redux 2.x and React Redux 2.x which no longer hot reload reducers ' + 'automatically. See https://github.com/reactjs/react-redux/releases/' + 'tag/v2.0.0 for the migration instructions.');
var didWarnAboutReceivingStore = false;
function warnAboutReceivingStore() {
  if (didWarnAboutReceivingStore) {
    return;
  }
  didWarnAboutReceivingStore = true;

  warning$2('<Provider> does not support changing `store` on the fly. ' + 'It is most likely that you see this error because you updated to ' + 'Redux 2.x and React Redux 2.x which no longer hot reload reducers ' + 'automatically. See https://github.com/reactjs/react-redux/releases/' + 'tag/v2.0.0 for the migration instructions.');
}
view-source:moz-extension://217edf57-d707-468e-b6b8-90fe450dc96c/js/background/backgroundLogic.js
  async getExtensionInfo() {
    const manifestPath = browser.extension.getURL("manifest.json");
    const response = await fetch(manifestPath);
    const extensionInfo = await response.json();
    return extensionInfo;
  },
    const manifestPath = browser.extension.getURL("manifest.json");
Error when attaching target: Error: Connection closed, pending request to server1.conn0.windowGlobal96636764161/consoleActor2, type startListeners failed

Request stack:
request@resource://devtools/shared/protocol/Front.js:292:14
generateRequestMethods/</frontProto[name]@resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:46:19
startListeners@resource://devtools/client/fronts/webconsole.js:310:34
attachConsole@resource://devtools/client/fronts/targets/target-mixin.js:465:26
    baseFrontClassDestroy resource://devtools/shared/protocol/Front.js:103
    destroy resource://devtools/shared/protocol/Front.js:71
    destroy resource://devtools/client/fronts/webconsole.js:385
    destroy resource://devtools/shared/protocol/Pool.js:199
    baseFrontClassDestroy resource://devtools/shared/protocol/Front.js:107
    _onTargetDestroyed resource://devtools/shared/commands/target/target-command.js:285
    _emit resource://devtools/shared/event-emitter.js:226
    emit resource://devtools/shared/event-emitter.js:172
    emit resource://devtools/shared/event-emitter.js:324
    _onTargetDestroyed resource://devtools/client/fronts/watcher.js:74
    _emit resource://devtools/shared/event-emitter.js:226
    emit resource://devtools/shared/event-emitter.js:172
    emit resource://devtools/shared/event-emitter.js:324
    onPacket resource://devtools/shared/protocol/Front.js:336
    onPacket resource://devtools/client/devtools-client.js:482
    send resource://devtools/shared/transport/local-transport.js:68
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
TypeError: context.contentWindow is null 7 ExtensionContent.jsm:620:28
TypeError: PrecompiledScript.executeInGlobal: Argument 1 is not an object. 5 ExtensionContent.jsm:575:25
resource://devtools/shared/builtin-modules.js
resource://devtools/server/connectors/js-window-actor/DevToolsFrameChild.jsm

Expected results:

No errors, no Problems.

Thanks!

The Bugbug bot thinks this bug should belong to the 'WebExtensions::Request Handling' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Request Handling
Product: Firefox → WebExtensions

Hello,

I did notice several of the mentioned errors (cannot specifically say which ones, but some do seem familiar) in the browser console during Nightly usage.

I however did not notice any noticeable issues which could have been caused by these.

Also I did not observe a pattern with which these errors occur and do not have any specific steps to reproduce the errors consistently.

For example, accessing https://www.facebook.com/ logged the Exception { name: "NS_ERROR_NOT_AVAILABLE", message: "Component returned failure code: 0x80040111 error, however on refreshing the page DOMException: JSWindowActorChild.sendAsyncMessage: JSWindowActorChild cannot send at the moment event-emitter.js:241:21 was logged. Closing the tab with the Facebook login page and opening it again, did not log the first error again or any error at all.

Do you by any chance have any consistent steps to reproduce these errors and wouldn’t mind to share them? Thank you!

Flags: needinfo?(wtds.trabalho)

The error message from the title is bug 1712335.

The TypeError: PrecompiledScript.executeInGlobal: Argument 1 is not an object. 5 ExtensionContent.jsm:575:25 one is bug 1403505

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(wtds.trabalho)
Resolution: --- → DUPLICATE
See Also: → 1403505
You need to log in before you can comment on or make changes to this bug.