Something seems to have changed with Wallaby or Chromedriver. After my test suite runs there are orphaned chrome instances present. During test execution I cannot run with the browser, only headless. When tests fail they no longer take a screenshot.
I am not sure what’s changed nor how to debug it. There is a recently opened issue https://github.com/elixir-wallaby/wallaby/issues/544
My chromedriver already matches my browser’s version. I have tried downgrading to 0.25 but no change in behavior.
This isn’t the first time there have been rogue processes left after a test. I wasn’t able to investigate them previously and I’m not sure how to investigate them now.
Direction is greatly appreciated.