Answered

Tests fails with "Error communicating with the remote browser. It may have died." message.

For some of our cloud runs we see tests failed with below messages. Observing the recording, looks like browser is closed suddenly before the test finishes. 


Error communicating with the remote browser. It may have died.
Driver: Firefox Driver
Driver verison: 0.31.0

The Firefox version used in VMs are is Mozilla Firefox (v103.0.1).

 

0
14 comments
Avatar
Greg Fangonil

We're seeing this with Chrome too.  The test will run and then browser immediately closes.

message='Error communicating with the remote browser. It may have died.
Driver: Chrome Driver
Driver verison: 103.0.5060.53'
2022-08-11 19:15:18 [pool-1042-thread-1] ERROR c.s.p.e.cloud.ExecutionListenerImpl - Error while getting browser logs
java.util.concurrent.ExecutionException: org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died.

0
Comment actions Permalink
Avatar
Joseph Hamdan

Hi Hasib/Greg,

1. Was anything changed recently on these VMs?

2. Do these errors happen locally, or only on the cloud VMs?

3. What's the Java version being used?

4. Are these errors intermittent or always happen?

5. In your User Execution Preferences > Advanced tab, could you please click Restore browser settings to default icon next to Chrome and Firefox, then try again? If you're running using an execution set, the same can be applied in Browsers tab if you edit the execution set.

Regards,
Subject7 Team

0
Comment actions Permalink
Avatar
Greg Fangonil

1. Was anything changed recently on these VMs? We had some patching done, but will look into ruling that out today.

2. Do these errors happen locally, or only on the cloud VMs? Both

3. What's the Java version being used? I'll check with SA's on this.

4. Are these errors intermittent or always happen? Intermittent.  Seems to happen on longer tests.

5. In your User Execution Preferences > Advanced tab, could you please click Restore browser settings to default icon next to Chrome and Firefox, then try again? If you're running using an execution set, the same can be applied in Browsers tab if you edit the execution set.  I'll give this a try today and run some tests.

0
Comment actions Permalink
Avatar
Greg Fangonil

To clarify on #1.  I thought I saw this happen prior to patching.  So that's what I meant by trying to rule it out.

0
Comment actions Permalink
Avatar
Greg Fangonil

Java version on VM's are java.version: 1.8.0_341

0
Comment actions Permalink
Avatar
Rex Feizi

Greg,

Does the Chrome base test also affected? If yes, are Chrome versions 104? If yes, do you know how to setup custom chrome driver ?

0
Comment actions Permalink
Avatar
Greg Fangonil

Rex,

Chrome version is 104.  

from the logs -> browserVersion: 104.0.5112.81, chrome: {chromedriverVersion: 103.0.5060.53

I do not know how to setup the custom chrome driver.  Are there instructions in help guide?  If so I can look there.

0
Comment actions Permalink
Avatar
Greg Fangonil

Continuing to get the same error with updated driver.

browserVersion: 104.0.5112.81, chrome: {chromedriverVersion: 104.0.5112.79

0
Comment actions Permalink
Avatar
Rex Feizi

Will reach on Monday to take a look. How many test are affected, and was this working before ?

0
Comment actions Permalink
Avatar
Greg Fangonil

Yes, this was working earlier this week.  We had some patching done Wednesday, but no browser updates.  There is a ticket in with our Ops team so they can take a look and maybe whatever was patched may be the reason.  Based on the execution sets I've used for testing about 1/3 of the tests are failing in the execution set. Prior to the patching all tests were passing.  Please reach when you can on Monday.  Both Hasib and I will be available.

0
Comment actions Permalink
Avatar
Joseph Hamdan

Issue inspected on a meeting and was to be monitored further. Please let us know if you still face it.

Regards,
Subject7 Team

0
Comment actions Permalink
Avatar
Greg Fangonil

After some triage, it was noticed there were duplicate servers for two of the servers appearing in Pool Management.  So new tests would close the browser for a test already running.  Xpoints were restarted and verified there were no duplicate servers in Pool Management.  The issue has been resolved and noted for future troubleshooting.

0
Comment actions Permalink
Avatar
Joseph Hamdan

Hi Greg,

Thank you so much for explaining, glad to hear that the issue is now resolved.

Have a great day!

Regards,
Subject7 Team

0
Comment actions Permalink

Please sign in to leave a comment.