Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[🐛 Bug]: Running automation testing with Chrome and Selenium causing unusual increase in network traffic #14855

Open
dhtt663 opened this issue Dec 5, 2024 · 4 comments
Labels
I-defect I-issue-template Applied to issues not following the template, or missing information. needs-triaging

Comments

@dhtt663
Copy link

dhtt663 commented Dec 5, 2024

What happened?

Steps to reproduce the problem

  1. Set up the automation test project with the following:
  • Selenium version 4.8.1

  • Java version 17

  • Chrome version 130.0.6723.116

  • Run tests in parallel using 4 threads

  • About 750 scenarios (around 30,000 steps)

  1. Integrate the project with Jenkins using this setup:
  • Jenkins version 2.462.3
  1. After the tests finish running on Jenkins, check how much server bandwidth was used
    Problem Description
    We have Chrome (version 130.0.6723.116) and Jenkins (version 2.462.3) installed on our server running CloudLinux v8.10.0 STANDARD for running automation testing with Selenium. Daily network traffic is around 55GB to 70GB per day (we monitor using vnstat tool on Linux). But when we ran automation testing from Jenkins with Chrome it caused an increase in the total network traffic to over 150GB per day. More details from vnstat as below:
     day        rx      |     tx      |    total    |   avg. rate     
------------------------+-------------+-------------+---------------     
2024-12-01   122.80 GiB |    2.25 GiB |  125.06 GiB |   12.43 Mbit/s     
2024-12-02   148.36 GiB |    2.90 GiB |  151.25 GiB |   15.04 Mbit/s     
2024-12-03    80.06 GiB |    1.93 GiB |   81.99 GiB |    8.15 Mbit/s     
2024-12-04    79.93 GiB |    1.90 GiB |   81.83 GiB |    8.14 Mbit/s     
------------------------+-------------+-------------+---------------      
sum of 4    431.15 GiB  |    8.98 GiB |  440.13 GiB |

The first two lines are the network traffic we running automation testing and the last two are when not running.

However, the issue does not happen on the previous Chrome version. For example, Chrome version 130.0.6723.116
which we are using for current automation testing.

Summary
Running automation testing with Chrome and Selenium causing unusual increase in network traffic

Additional Data
Category: Network / Downloading
Chrome Channel: Stable
Regression: N/A

How can we reproduce the issue?

We have 2 console log runs with 2 versions of Chrome: 130.0.6723.116 and 127.0.6533.119.
https://github.com/dhtt663/Selenium-with-Chrome-version.git

Relevant log output

1. The console log output when run with Chrome version: 130.0.6723.116
2. The network traffic when run with Chrome version: 130.0.6723.116
3. The console log output when run with Chrome version: 127.0.6533.119
4. The network traffic when run with Chrome version: 127.0.6533.119 
Please refer to the following to view the log details:
https://github.com/dhtt663/Selenium-with-Chrome-version.git

Operating System

CloudLinux v8.10.0 STANDARD

Selenium version

selenium-java version: 4.8.1

What are the browser(s) and version(s) where you see this issue?

Chrome version: 130.0.6723.116

What are the browser driver(s) and version(s) where you see this issue?

Chromedriver 130.0.6723.116

Are you using Selenium Grid?

No response

Copy link

github-actions bot commented Dec 5, 2024

@dhtt663, 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
Copy link
Member

VietND96 commented Dec 5, 2024

Did you try to disable this feature in Chrome? https://www.selenium.dev/blog/2024/chrome-browser-woes/

@pujagani pujagani added the I-issue-template Applied to issues not following the template, or missing information. label Dec 13, 2024
Copy link

Hi, @dhtt663.
Please follow the issue template, we need more information to reproduce the issue.

Either a complete code snippet and URL/HTML (if more than one file is needed, provide a GitHub repo and instructions to run the code), the specific versions used, or a more detailed description to help us understand the issue.

Note: If you cannot share your code and URL/HTML, any complete code snippet and URL/HTML that reproduces the issue is good enough.

Reply to this issue when all information is provided, thank you.

@pujagani
Copy link
Contributor

Can you please confirm if this occurs with the latest version of Selenium? We only triage the latest versions since we don't do patch releases for older versions. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I-defect I-issue-template Applied to issues not following the template, or missing information. needs-triaging
Projects
None yet
Development

No branches or pull requests

3 participants