woohaaha
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 Chrome zombie processes · Issue #544 · elixir-wallaby/wallaby · GitHub
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.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #ai
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
michallepicki
Did you try downgrading chrome and chromedriver versions used as well, just for the time being?
woohaaha
I’m not sure what are the risks involved in downgrading Chrome. Since there are other projects on this computer I’d rather not mess with it. Seems like Google does not encourage downgrading Chrome versions.
woohaaha
Update:
I was looking at my screenshots directory and saw that the last screenshot was taken a day before my upgrade from 0.23 to 0.25. I then noticed that I had to change:
Ok, great, now browser appears.
However, screenshots are:
take_screenshot(session)the directory isn’t displayed in the terminal’s output.I double checked these settings but they seem to have stayed the same. Any ideas? I have also upgraded to 26.2 with no luck.
mhanberg
Hi,
To take screenshots on failure, you must configure
:screenshot_on_failureto be true, and this only works when using thefeaturemacro.You must pass the
log: trueoption totake_screenshotfor it to print to the terminal.woohaaha
Thank you so much!
I got screenshots working on failure but now if I test with
chromedriver: [headless: false]it may be opening two browsers. The second browser appears to be doing the testing and is then closed while the first one is left open but blank.There are two screenshots taken on a failure. One is blank, the second is the accurate page where the failure happened.
Am I still misconfigured?
Thank you so much for your great work on Wallaby!
mhanberg
You are likely starting a session manually in addition to using
use Wallaby.Featurein your test.If you are already using your own
ExUnit.CaseTemplate, you probably want to replaceuse Wallaby.Featurewithimport Wallaby.Featurewoohaaha
you’re on fire!
thank you so much!!!
we’re back in business
