Soooo many chrome-sandbox processes still on top after all tests are done.

[yukinying]

Soooo many chrome-sandbox processes still on top after all tests are done.

[yukinying]

Do you have some quick samples (or urls) that can be shared? The processes become zombies which may mean a parent process dies before the child processes are cleaned up.

[caryyu]

Well, you can see code snippet below, i just wanna parallel every single testcase by multiple threads, but each testcase will start a new chrome process then quit after it's done. Have you ever met this issue before if you're trying to run a huge numbers of testcases ? Anyway , i'm going to upgrade your Docker Image first to make sure if it is still .....

BTW: i've used RemoteWebDriver connecting to this Docker Image.

public class ParallelSolvingTest {
    private static Log log = LogFactory.getLog(ParallelSolvingTest.class);
    private ThreadLocal<WebDriver> wd = new InheritableThreadLocal<>();
    
    @BeforeMethod
    public void beforeMethod() {
        WebDriver webDriver = DriverUtility.openDriver();
        wd.set(webDriver);
    }

    @AfterMethod
    public void afterMethod(){
        WebDriver webDriver = wd.get();
        if(webDriver != null) {
            webDriver.manage().deleteAllCookies();
            webDriver.quit();
        }
    }
}

[yukinying]

Did you use standalone mode or hub mode? I used protractor and I did not see any zombie processes after sending 100 individual protractor tests in standalone mode.

[caryyu]

I'm calling the address like this http://x.x.x.x:4444/wd/hub, maybe this is hub mode.. what you mean the standalone mode is just like connecting straight forward to ChromeWebDriver port right?

[yukinying]

Yes, If you hit it with wd/hub, it is using the hub mode. I tried hub mode as well, and all 100 tests finished without leaving any zombie process. I think you may want to look at the logs and see if there are any crashes, which would have caused the zombie processes to hang around.

[caryyu]

In the log, there are lots of WARN - Exception: no such element: Unable to locate element occurring, i'm not very sure if it's effecting on ..

[yukinying]

Honestly, I have no clue unless I can reproduce it on my machine. I understand your test cases may be more comprehensive thus my tests are not identical as yours. What I usually do with these kind of errors is to set up an environment without docker and verify if this is caused by the docker setup or not.

[caryyu]

I've upgraded to 3.6.0, the issue is gone. maybe version causes this.