Open Bug 835037 Opened 12 years ago Updated 2 years ago

Remote debugger can attach to local Firefox with same process id

Categories

(DevTools :: about:debugging, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: tetsuharu, Unassigned)

References

(Blocks 1 open bug)

Details

Remote devtools can attach to local Firefox [Environment] * http://hg.mozilla.org/mozilla-central/rev/a207f33adc1a * devtools.debugger.remote-host=localhost * devtools.debugger.remote-port=6000 [Step to reproduce] 0. No running any servers on localhost:6000. 1. Start Firefox (e.g. This PID is 1000) 2. Open Browser debugger from Firefox (PID:1000) & close it. 3. Open "Connect..." command from tool menu on Firefox (PID:1000). 4. Start remote devtools with connecting to localhost:6000. [Result] * Remote devtools can attach to parent Firefox (PID:1000). * If we open debugger pane in its devtools-box after attach to parent Process' browser chrome, Firefox (PID:1000) will freeze. (This is very annoying!) [Expectation] I propose that we should make Firefox remote debugging cannot attach to same prrocess without create a new process which remote debugger runs on. But I don't understand very well about the current remote debugging architecture. There may be more good idea for resolve this bug.
Getting the remote debugger to debug chrome JavaScript is actually a feature, which should get more use once we enable chrome debugging for Fennec and B2G. The problem in this case is that when the Browser Debugger finishes the socket listener remains open. It would be nice to close it automatically, if we can avoid hurting Marionette (see bug 793760).
Component: Developer Tools: Framework → Developer Tools: Debugger
OS: Mac OS X → All
Hardware: x86_64 → All
We've made it harder to get into this situation by using a different port for browser debugger now.
Priority: -- → P3
(In reply to Panos Astithas [:past] from comment #2) > We've made it harder to get into this situation by using a different port > for browser debugger now. Do we still want to take other precautions here? Or can we consider this resolved.
Summary: Remote devtools can attach to local Firefox which has same process id → Remote debugger can attach to local Firefox with same process id
Product: Firefox → DevTools
Component: Debugger → about:debugging
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.