Closed
Bug 907841
Opened 11 years ago
Closed 10 years ago
Browser Debugger fails silently if port 6080 in use
Categories
(DevTools :: Debugger, defect, P3)
DevTools
Debugger
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 958498
People
(Reporter: myk, Unassigned)
Details
(Whiteboard: [chrome-debug])
If port 6080 is already in use when I select Tools > Web Developer > Remote Debugger, nothing appears to happen, except that the following exception is reported to the Browser Console:
uncaught exception: 2147746065
At the very least, Firefox should tell me about the problem; even better would be to resolve it automagically, f.e. by using a different port.
Updated•11 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [chrome-debug]
Comment 1•11 years ago
|
||
We have code to retry different port numbers here:
http://mxr.mozilla.org/mozilla-central/source/toolkit/devtools/server/tests/unit/test_dbgsocket.js#122
But we are also planning to use a local domain socket for the Browser Debugger when those are implemented (maybe they already are?). I'm leaning towards the latter if this bug is not considered high priority.
Updated•11 years ago
|
Priority: -- → P3
Comment 2•11 years ago
|
||
Not specific to the browser debugger, but if the port is not available, then I think an alert should be shown if devtools.debugger.show-server-notifications is true.
Comment 3•11 years ago
|
||
Sorry, I didn't see bug 958498.
Comment 4•10 years ago
|
||
This should be fixed as part of bug 958498. Marking as duplicate.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•