[🚀 Feature]: we are facing issues regarding memory usage when running selenium testcases on chrome and as 4.2Gb memory is utilized the chrome driver shuts off and we see NoSessionException

[Amanyadav12345]

Feature and motivation

we might need a flag so that we can reduce the memory issue of chrome maybe GC calls at random Chrome

Usage example

continuous increase in memory usage which will lead to failed testcases

[github-actions]

@Amanyadav12345, 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!

[diemol]

That is something that only Chrome can control. Not the Selenium code.

[github-actions]

Hi, @Amanyadav12345.
This issue has been determined to require fixes in ChromeDriver.

You can see if the feature is passing in the Web Platform Tests.

If it is something new, please create an issue with the ChromeDriver team.
Feel free to comment the issues that you raise back in this issue. Thank you.

[Amanyadav12345]

As per comment #1, the issue is related to Selenium Java, which is out of scope for TE to triage. Hence, adding the TE-NeedsTriageHelp label and requesting assistance from the Dev team for further inputs on this issue.

this is the comment I received from google issue services
https://issues.chromium.org/issues/384844008

[diemol]

You do need to provide them with much more information. Screenshots are not enough. They get many reports per day, so if you want them to pay attention to it, you need to provide code to reproduce the issue and more detailed information.

[github-actions]

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