remote-debugging-port is not there in "netstat -ano" output

275 views
Skip to first unread message

Edward Zhou

unread,
Jul 6, 2019, 3:50:17 AM7/6/19
to Chrome DevTools
On Windows 10, I open use below commands:
C:\Users>cd C:\Program Files (x86)\Google\Chrome\Application
C:\Program Files (x86)\Google\Chrome\Application>chrome.exe --remote-debugging-port=9223

It does open a Chrome instance. However, when I use 
netstat -ano

I don't see 9223 in the output which means I cannot connect to host chrome for debugging.

Try 2 machines with the same result. Can anyone shed some lights?

Larry

unread,
Jul 6, 2019, 1:46:32 PM7/6/19
to google-chrome-...@googlegroups.com
@Edward: It worked for me.  
Using your commands, my netstat -ano shows:
  TCP    127.0.0.1:9223         0.0.0.0:0              LISTENING       15080
I verified the PID(15080) from task manager as chrome.exe.

From the chrome session, use the URL chrome://version to display the launch command:
  Command Line chrome.exe --remote-debugging-port=9223 --flag-switches-begin --flag-switches-end
  Executable Path C:\Program Files (x86)\Google\Chrome\Application\75.0.3770.80\chrome.exe
to verify how chrome was started.

If chrome is already running, starting chrome.exe from the command line opens a new window on the existing chrome process
AND ignores any new --switches.


--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/a89bfb6d-062b-4382-ad7f-5ef36b7f06c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Reply all
Reply to author
Forward
0 new messages