Closed erickubenka closed 1 month ago
Two options. Either some swap or something like that becomes full and therefor session got killed or unavailable. Or (my guess) a timeout of 5 hours is somewhere defined for a session and therefor browser got killed.
Why I guess its the second option? Because in server logs i can see that cpu drops down two times after application start was 5 hours ago.
Possible workaround Do a restart when Error for HomePage Instantiation occurs.
And find were timeout is set.
unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed with ChromeDriver Selenium
First attempt is to increase shm size to 2g as recommended on docker-selenium containers as well. Will check if this helps, otherwise we go for a restart option inside the code base as mentioned before.
Did not work, but now implemented a simple restart to see if this will avoid this issue. So baiscally chrome driver will create a new session, when the error message was detected
Successfully tested on server and runnign instance today. automatic restart worked fine.
Describe the bug Somehow after a long duration of run (greater > 5hours) the ChatWindow of WhatsApp become anvailable for the Framework und therfor an instance of
HomePage
can not be instantiated.Full Trace: