search

rubycdp / ferrum

Headless Chrome Ruby API
https://ferrum.rubycdp.com
MIT License
1.76k stars 127 forks source link

ProcessTimeoutError after upgrading to google-chrome-stable 127 #482

Closed dventulieri closed 3 months ago

dventulieri commented 3 months ago

Describe the bug

We updated our servers to google-chrome-stable 127 this morning. Since then, we've been unable to run Ferrum::Browser.new because we constantly get Ferrum::ProcessTimeoutError (Browser did not produce websocket url within 10 seconds, try to increase:process_timeout. See https://github.com/rubycdp/ferrum#customization) errors.

We've tried increasing the timeout, but it doesn't fix the issue.

We never ran into this error prior to updating to Chrome 127. We are not able to connect to the WS URL at all.

This does not occur on my Mac that is also running Chrome 127.

To Reproduce

With Ruby 2.6.9 and google-chrome-stable-127.0.6533.119-1.x86_64 on Amazon Linux 2, try starting a new Ferrum browser with Ferrum::Browser.new. It will hang and then raise a Ferrum::ProcessTimeoutError after n seconds.

Expected behavior Ferrum::Browser.new should return a new browser object.

Screenshots image

Desktop (please complete the following information):

Additional context This was not happening prior to updating Chrome. Unfortunately, Google makes it difficult to downgrade to an older version of Chrome.

dventulieri commented 3 months ago

Closing as this is definitely a bug with google-chrome-stable 127. I am not able to start google-chrome-stable via the CLI. I've logged a ticket with Google and rolled back to 126.

route commented 3 months ago

You should probably filter out snap as well.