Closed Bug 1514215 Opened 6 years ago Closed 6 years ago

Error message from about:debugging#addons > Debug

Categories

(DevTools :: about:debugging, defect)

Product:
DevTools
Component:
about:debugging
Version:
64 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1525533

People

(Reporter: t20, Unassigned)

Details

Attachments

(1 file)

TempAddonError.png
(deleted), image/png
Details
Attached image TempAddonError.png (deleted) —
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 Steps to reproduce: 1. Set up any of several examples of Webextensions use. 2. Visit about:debugging#addons 3. Load the temporary addon (the example) 4. Try out the addon (it works) 5. Click Enable add-on debugging 6. Under Temporary Extensions, click Debug Actual results: Get window containing error message: "Connecting to localhost:55938, ws: false [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIInputStream.available]" nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)" location: "JS frame :: resource://devtools/shared/base-loader.js -> resource://devtools/shared/security/socket.js :: onInputStreamReady :: line 329" data: no] onInputStreamReady@resource://devtools/shared/base-loader.js -> resource://devtools/shared/security/socket.js:329:9" Expected results: The debug constellation of panes should have appeared. It does, in fact, appear if I close the error message window and click OK to a new window that appears: "An incoming request to permit remote debugging connection was detected. A remote client can take complete control over your browser!"
Hi David, Can you give the sample of the temporary addon?
Flags: needinfo?(t20)
Component: Untriaged → about:debugging
Product: Firefox → DevTools
Sure. Here is a tiny extension that produces the error message ==== Browser Toolbox connection status: Connecting to localhost:54203, ws: false [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIInputStream.available]" nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)" location: "JS frame :: resource://devtools/shared/base-loader.js -> resource://devtools/shared/security/socket.js :: onInputStreamReady :: line 329" data: no] onInputStreamReady@resource://devtools/shared/base-loader.js -> resource://devtools/shared/security/socket.js:329:9 ==== Manifest: ==== { "manifest_version": 2, "name": "Bug1", "version": "0.2", "icons": { "48": "icons/link-48.png" }, "permissions": [ "activeTab", "contextMenus", "notifications" ], "background": { "scripts": ["PM_bg.js"] } } ==== PM_bg.js: ==== // S: Promise to show string in notification box function S(Msg,Title) { return browser.notifications.create({ "type": "basic", "iconUrl": browser.extension.getURL("icons/link-48.png"), "title": Title, "message": Msg}); } // S S('bg running','Direct from bg').then(empty).catch(err); /* window.addEventListener('load',function(e) { S('bg loaded','Direct from bg').then(empty).catch(err); }, true); */ // Functions function empty(ignored) { console.log('doing nothing'); } // empty function err(Msg) { console.log('*** '+Msg); } // err // End ====
Flags: needinfo?(t20)

I'm experiencing the same bug.

Submitted a similar bug report via the web-ext project: https://github.com/mozilla/web-ext/issues/1489

Rebooted computer and bug is gone

I just tried removing the temporary extension, restarting Firefox, then installing the temporary extension. Clicking "debug" brought up the debugger and its popunder permission dialog as documented, without this bug, three times in a row. My conclusion is that this bug cannot easily be replicated.

David, have you tried using web-ext?

https://www.npmjs.com/package/web-ext

Sun, No, I have been trying to avoid command-line tools because as a Windows developer who used command lines for many years I am not looking forward to going backward. Can I use GitHub Desktop to install and use web-ext instead of nodejs? I once installed nodejs and found it inefficient (it spend many seconds to download each dependency module of an app separately) and difficult to use (command-line) as compared with other tools that I can invoke automatically with just a keystroke or mouse click such as my text editor, PHP, Apache, JavaScript, and Mongoose.

Hey David, I agree command line can be more work at times.

Unfortunately, web-ext is a command line utility and it does require Node on your computer.

About dependencies, once Node and NPM (which is bundled with Node) is installed on your computer, running npm install web-ext -g will take care of installing all dependencies for you.

I don't know much about Windows so I can't be much help.

Good luck!

This should be fixed on Nightly thanks to Bug 1525533. We are no longer spawning a new Firefox instance to debug local addons, so the connection issues should be gone. I will close as duplicate, feel free to reopen if you still have the issue.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE

To comment 9: When you say "We are no longer spawning a new Firefox instance to debug local addons", which public stable release number is the first that this applies to? This may be relevant to people who encounter this problem.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: