Retrieve DevTools port from ChromeDriver session
thelightcosine opened this issue · comments
Currently when starting a new session the chrome instance is spawned with the remote-debugging-port set to a random high port. There is no way, aside from searching through ChromeDriver logs, to retrieve what port was passed to DevTools. I need to be able to tell an external 3rd party program how to talk to the Chrome session hound has opened.
You can set --verbose with the driver, but you can also use --remote-debugging-port=xxxx, but i couldn't get it to talk between the driver and hound when i did that.
If you pass the --remote-debugging-port option the whole thing just hangs and Hound craps out. I'm fine with the randomly selected port, but I need a way to programmatically access what that port is.