[BUG] Playwright-chromium (>1.5.0) does not exit properly (hangs) when started in docker

Context:

• Playwright Version: playwright-chromium 1.5.0, 1.5.1 (in 1.4.0 everything was fine).
• Operating System: Windows 10/MacOS Catalina + Docker
• Node.js version: 12.18.3
• Browser: Chromium
• Extra: Docker image based on PW:bionic; mocha for running tests;

Bug description: Playwright hangs after tests execution when running in Docker. It simply does not do anything (as per logs).

Repro steps:

1. Unpack sample project, go to root folder
2. Run the following command: docker-compose up --build --abort-on-container-exit --exit-code-from e2e > test_run.log
3. Check test_run.log. Once all tests are finished, you will see the following lines in log:

[36me2e_1 | ##teamcity[testFinished name=‘Test_1 Test 5 - UI Open Search page, find user and open it - chromium’ duration=‘7284’ flowId=‘28’] e2e_1 | ##teamcity[testSuiteFinished name=‘Test_1 Google and Twitter checks - chromium’ duration=‘’ flowId=‘28’]

But the process will stay alive and docker container will never exit (at least in 2 hours). qa-automation.zip

I was also able to reproduce this behaviour on my Mac using provided test project.

[pavelfeldman]

The hang is fixed and will be released with 1.5.2. shortly. The Chromium issue is about service workers, is now filed upstream and I’m working on a fix there.

[pavelfeldman]

Reduced test case:

await page.goto('https://twitter.com');