[🐛 Bug]: The standalone driver with a video recorder sidecar takes too long to stop the recorder (versions 20260303 and above)

[javiertuya]

What happened?

I’m running a standalone Chrome driver with a video recorder sidecar. On container versions 20260202, stopping the video recorder takes less than 2 seconds, but after upgrading to versions 20260303 or 20260404, it now takes 10 seconds. I’m still using the old method with SE_VIDEO_EVENT_DRIVEN=false.

To reproduce, copy the following files to a temporary folder:

compose-test.yml

run-test.sh

From the temporal folder, run run-test.sh. For each version 20260202 and above, the script spins up a standalone driver container with a video recorder sidecar, waits a few seconds to allow the video to generate, then stops the recorder and shows the time it took to stop the recorder.

NOTE1: Run this from a Linux machine (I'm using Ubuntu). If you run it from Windows (e.g., using a Visual Studio Code Bash terminal), you won’t see the 10-second time.

NOTE2: This might be related to the issue. #3093 that got fixed in #3105

Command used to start Selenium Grid with Docker (or Kubernetes)

Starting standalone Chrome driver and video recorder using Docker Compose (see files above).

Relevant log output

Output of `run-test.sh` (docker compose outputs removed)

Time to stop container 20260202: 1803 ms
...
Time to stop container 20260222: 1575 ms
...
Time to stop container 20260303: 10306 ms
...
Time to stop container 20260404: 10301 ms

Operating System

Ubuntu 24.04

Docker Selenium version (image tag)

4.42.0-20260303 and above

Selenium Grid chart version (chart version)

No response

[github-actions]

@javiertuya, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

@javiertuya, can you replace image tag nightly and try again?
Looks like only Ubuntu can reproduce it, since I tried the script you share on macOS, it could not be reproduced also.

[javiertuya]

@VietND96 Thanks for the quick response. I have prepared a repo to reproduce the issue from GitHub Actions: https://github.com/javiertuya/selenium-docker-test. Here are the results, including the nightly build (worflow job test-video-close):

Time to stop container nightly: 10106 ms
Time to stop container 20260202: 1563 ms
Time to stop container 20260222: 1246 ms
Time to stop container 20260303: 10103 ms
Time to stop container 20260404: 10104 ms

NOTE: Something similar happens with the dynamic grid: the time to close the driver in version 20260202 is around 7 seconds, but in version 20260404 and nightly, it’s around 37 seconds. The repo https://github.com/javiertuya/selenium-docker-test also includes a workflow job (test-dynamic-grid) that demonstrates this. I can also reproduce it on Windows. I guess that in both cases, the video container fails to shut down and stops only after a timeout.

Let me know if you’d like me to submit a separate issue for the dynamic grid.

[VietND96]

Thanks for your very details info, I also have setup a dev Ubuntu VM that can reproduce the delay in shutdown, hopefully can fix it there.

[VietND96]

Based on your tests, I checked with Nightly build and saw it works. New image 20260505 is deployed

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.