Open berkeroguz opened 7 months ago
@berkeroguz what is your Selenoid version?
We may need to add se:cdpVersion
support.
Hi again, sorry for my late return.
Selenoid version : latest.
I don't use a particular version.
I experience exact the same issue. Is there a workaround known for now?
I couldn't find solution still. But for now, I use on windows. There is not problem on windows. There is problem only on mac which is arm64 ( like M1 )
@berkeroguz Chrome has no release for Linux ARM64 and will not work on Mac M1.
@berkeroguz : ok, I see, strange thing is that it seems to work for a colleague also on mac arm64 (M1) with same docker desktop version etc as me, so did not find out yet what is really different to find out a workaround (use windows is no option atm)... @vania-pooh : do your proposed changes fix the issue and if yes, is there a plan to get this fix merged?
@aplanche: not sure. If you provide some example source code to reproduce this - we could check.
unfortunately did not find a simple usecase to reproduce, currently only reproducible on our internal project. @berkeroguz : do you know a simple usecase to reproduce the issue on a public project?
Hi everyone, I've an issue.
When i start to my test, I am facing below problem.
2024-02-19 16:28:40 ChromeDriver was started successfully. 2024-02-19 16:28:43 X connection to :99 broken (explicit kill or server shutdown).