search

twalpole / apparition

Capybara driver for Chrome using CDP
MIT License
363 stars 46 forks source link

cannot launch Chrome app if test suite is interrupted #38

Open patrick99e99 opened 4 years ago

patrick99e99 commented 4 years ago

Mac OS X 10.10.5 Chrome Version 79.0.3945.130 (Official Build) (64-bit)

Steps to reproduce:

1) Chrome icon is on dock 2) Capybara test is started 3) Chrome icon on dock bounces a single time, test is running 4) Press ctrl-c to stop test in progress 5) Click Chrome icon on dock

Observe the chrome icon bounces a single time but app does not launch.

ps shows that chrome is not running, yet it will not launch without a reboot.

patrick99e99 commented 4 years ago

This is what my activity monitor looks like after a day of working on getting my feature specs passing with Apparition.

Screen Shot 2020-01-23 at 6 09 10 PM
evgeniradev commented 4 years ago

This happens on my system too: Mac OS X 10.13.6 Chrome Version 79.0.3945.130

twalpole commented 4 years ago

I'm wondering whether this has something to do with older versions of OSX

patrick99e99 commented 4 years ago

I actually upgraded to 10.15 and still experience this. If I run tests, and then ctrl-c and stop the tests, I see that the process of Chrome was not killed.

shepmaster commented 4 years ago

I've seen this as well on macOS 10.15.5. My daily driver is Chrome Canary, but I use stable Chrome for video calls and the like. Apparition uses stable Chrome (which is what I'd want), so I might not notice this for a day or two.

I do have to really kill RSpec to trigger this. Pressing Ctrl-C once will interrupt RSpec and it will shut down cleanly. Pressing it twice will kill it immediately, and that's when the rogue Chrome processes will stick around.

Our test suite also spins up some Redis instances that exhibit the same behavior in the same circumstances, so this may not be an Apparition-specific issue.