-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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]: Browser closes after a short time #2084
Comments
@GuillaumeFradet, 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! |
I saw in the chart YAML that the image tag is |
Does your deployment have ingress upfront? if yes, can you try a trick by opening Grid URL with schema HTTPS to see how it behaves? |
No sorry i don't have ingress upfront |
Yes, it looks similar the same behavior was reproduced here - SeleniumHQ/selenium#13393 (comment) |
I see that the issue you mentioned has just been marked as fixed, which means that the problem has been solved? |
We mark them as fixed then the code has landed, however we still need to do a new release. |
Ah, the background is the issue relates to the Grid with |
While waiting for the patch to be deployed, I tried to disable noVnc. I did see the start_vnc option with the value false.
|
If disable noVNC, I think it should be |
Ok I have set it too but it still seems activated as you can see `kubectl get scaledjob selenium-chrome-node -n selenium-grid -o yaml
|
Ah ok, misunderstood your requirement. Those 2 ENV are used to disable the process in containers only. For the Grid UI, e.g you want to disable the recorder button or prevent the user from accessing the live preview of a session, I guess it does not support. That feature needs to be implemented on the upstream repository. @diemol, correct me if any missing |
In fact I wanted to see if disabling it, would remove the error since it seems to come from NoVnc.Ok, I'll keep looking for another solution if it's not supported. |
You need to disable |
Ok thanks, it does hide the camera preventing vision, but the browser still crashes after several minutes not finishing the process. |
What does this mean in detail? Can you describe this better please? |
I get the same result by setting the noVnc , vnc and start_xvfb options to false @diemol Ok I'll try with the nightly @VietND96 |
Those flags enable or disable VNC. Can you share the Grid log and the test log? |
Here are the node logs for my last test:
An test log : @diemol |
The Grid log seems incomplete. |
Although it was the entire log of the pod containing the Chrome node, I have this coming from the pod containing the hub. The HTTP connect time out error is raised when the browser is cut off and the connection becomes impossible.
|
Looks like a command is timing out, but it is not clear as the log from the Node is incomplete. You said that this was working fine before, which version were you using? |
I have 3 clusters, 2 are on version 4.11.0-20230801 and 1 on version 4.16.1-20231212. Right now, I'm running tests on the nightly version. Here's another log from one of my last tests for the chrome node [node] [[node.driver-configuration]] Starting Selenium Grid Node... |
My question is if things are still working with the previous version and when did it stop working? |
It doesn't work with either 4.11 or 4.16 since monday. It was working the previous friday |
OK, so if it is not working with 4.11, which was the previous version, and the Selenium components have not changed since then... what is your reasoning for this as a Selenium issue? Have you tried to troubleshoot your test and your system under test? |
Because I haven't changed anything between Friday and Monday, neither in the code nor in the test, and now the bug occurs when the grid window turns white, which didn't happen before. |
The Grid window turns white on 4.11 as well? |
OK, 4.11 has not changed, as we do not patch old versions. You need to check and trace what changes might have happened in your environment. |
This message will show when the live preview is opened on UI. It would be the IP of Node pod.
In this case, can you check in the cluster, is there any e.g network policy applied in between that could drop the connection? |
As I continued searching, I found out that my problem was coming from the RAM. |
@GuillaumeFradet, is that fine in recent versions with the increase resource requests/limits? |
@VietND96 I am still on 4.16 where indeed I no longer have this issue since increasing the resources. I had quickly tested 4.18 where I did not encounter the problem. |
I am closing this since there is no report further and the resolution is increasing the resources |
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?
Since today, whereas before it worked perfectly.
The browser seems to close after a few minutes.
However, I haven't changed anything in my configuration.
Have you added a timeout somewhere?
As you can see from the screenshot, there's no longer a browser present in the session, yet the session remains active and the script continues to run on it.
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Kubernetes
Docker Selenium version (image tag)
4.16.1-20231212
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: