We are attempting to do load testing for self hosted Jitsi meet using Jitsi meet torture.
Currently, setup selenium hub and selenium node on the same machine
Selenium Grid - Version 3.141.59
Chrome browser - Version 84.0.4147.135 (Official Build) (64-bit)
Chrome Driver (32 bit) - Version 84.0.4147.30
Here are the commands used to setup:
java -jar selenium-server-standalone-3.141.59.jar -role hub
java -Dwebdriver.chrome.driver=chromedriver -jar selenium-server-standalone-3.141.59.jar -role node -maxSession 1 -hub http://localhost:4444/grid/register -browser browserName=chrome,version=84,platform=WIN10,maxInstances=1
mvn test -Dorg.jitsi.malleus.conferences=3 -Dorg.jitsi.malleus.participants=3 -Dorg.jitsi.malleus.senders=1 -Dorg.jitsi.malleus.audio_senders=2 -Dorg.jitsi.malleus.duration=300 -Dorg.jitsi.malleus.room_name_prefix=hamertesting -Djitsi-meet.tests.toRun=MalleusJitsificus -Djitsi-meet.instance.url=“https://jitsiserver03.com”
I can see that it attempts to starts 3 conferences each with 3 participants. However, some of the participants fail to join the conference. Here is the error I see in logs:
(Session info: chrome=84.0.4147.135)
I see above error for 4 participants only. Other 5 participants ( out of 9) are able to join conference successfully.
For all the 9 participants (including the 5 which are able to join conference), I see following warning:
org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from renderer: 18.527
Looking at Jitsi meet torture source code, it seems TimeoutException is due to Chrome bug.
It looks like APP is not defined error comes for the participants for which Chrome is not loading the Jitsi meet page.
As stated above, error comes only for some of the participants but not for the others.
Any advise on what could be the problem? Do we need to test with other version of Chrome etc?