Steven Holdsworth

I had a faulty Nodejs plugin in sublime which messed with the loading of the PATH when sublime was launching. Check your Sublime Console when you start sublime, ensure PATH...

@solshark try looking @ https://github.com/holsee/chroxy which runs chrome as a service (now including a Dockerfile see the README) and has a convenient mechanism through https://github.com/holsee/chroxy_client to obtain chrome endpoints which...

Hi, thanks for reporting. The logs suggest that the connection is being closed on the client-side (Upstream): ``` 12:16:46.925 pid= module=Chroxy.ProxyServer [debug] Upstream socket closed, terminating proxy ``` Which once...

I have confirmed my hypothesis and have created 3 videos which highlight how this was done, these are all time sync'd so run them side by side: Client Shell: https://asciinema.org/a/JV2lWPbVl7wj96WAMdFTjXrDm...

I can only diagnose based on the information you provide and what you provided was a clear code path that the client is failing to establish a connection more specifically...

I am performing a simple test to try and recreate the issue: Set pool size to 10 instances of Chrome in Chroxy and start server: ```sh export CHROXY_CHROME_PORT_FROM=9222 export CHROXY_CHROME_PORT_TO=9232...

I have been able to put the system into an error state after on average between 1.5k to 3.5k tests. This is indeterministic and the system is recovering in most...

Looks like I have implemented this and forgot: https://github.com/holsee/chroxy/blob/a1997bd12c26dbd62c6653405af8c99b7fb01f87/lib/chroxy/chrome_server.ex#L132-L137 I would suggest we document this in the README or we add that ENV VAR as something baked in that will...

bump

Chrome is an interesting beast when it comes to memory, it's a thirsty boy. Automatic recycling of chrome instances internally could be a solution, having a the way connections and...