I have a Sidekiq job that uses Capybara, deployed on a Heroku dyno. I run into the following issue even with Sidekiq concurrency=1.
When run asynchronously, the jobs sometimes return the following error:
Selenium::WebDriver::Error::UnknownError: invalid argument: can't kill an exited process
But never ever synchronously on Heroku 🤔
When I look at the Selenium debug logs, I see:
This thread gives a fix for a similar but ultimately different issue also involving
$DISPLAY. However, I ssh'ed in and set $DISPLAY to
[:0.0] to no avail.
can't kill an exited process. However, my versions are compatible, using latest Selenium, Firefox, and geckodriver. And yes, I'm running headless=true.
ThreadError: can't create Thread: Resource temporarily unavailable
Selenium::WebDriver::Error::WebDriverError: unable to connect to geckodriver 127.0.0.1:4457
Selenium::WebDriver::Error::TimeoutError: Connection refused (os error 111)
Error R14 (Memory quota exceeded)
User contributions licensed under CC BY-SA 3.0