-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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]: NullPointerException while using DevTools instance with JDK 11 Http Client #12882
Comments
@pujagani, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
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. |
What happened?
Using JDK 11 Http Client prevents reusing of DevTools instance. Earlier, this was not a problem since Selenium used a single instance of AsyncHttpClient and it was only closed when the JVM shuts down. But with the JdkHttpClient, Selenium uses a new instance each time and closes it too.
Changes made as part of #11345, which assigns the client to null while closing causes an NPE when re-using DevTools instance. The changes were made to prevent memory leaks.
I am not sure about the right approach to address this. I will need to look into it further.
How can we reproduce the issue?
Relevant log output
Operating System
macOS Ventura
Selenium version
Java 4.13.0
What are the browser(s) and version(s) where you see this issue?
Chrome 117
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver Version: 117.0.5938.149
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: