thelightcosine

@holsee oh yes, and we are using Chroxy 0.6.3 ChroxyClient 0.3.0 ChromeRemoteInterface 0.3.0 (mandated by ChroxyClient, although ChromerRmoteInterface is now up to 0.4.1) Google Chrome 80.0.3987.87 unknown running on CentOS...

@holsee Here's the problem with that analysis. When we get in this state, closing and restarting the client side does absolutely nothing for us. It comes right back up and...

@holsee Wow, what a response! I apologise for how my last comment may have come across. You're correct that your analysis is valid, what i should have said is that,...

I would very much like this fixed as well if there's not a reason for the retries being stripped out. it also affects my use case

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...