Closed parthibd closed 5 years ago
Is this problem could be related to setting the same marionette port when starting the driver ?
Is this realted to my error ?
Let me get this right . Multiple drivers are running in the same event loop . So they share the same thread . And you are using a poolexecutor to run to execute webdriver commands . So do you think its a thread safety issue ?
I believe the main reason for this issue is that even if I try to set a marionette port in whalesong , geckoriver doesn't start marionette on the choosen port . So the first window opens fine but when later instances start up they try to connect to the same port . Am I right ?
I think whalesong should set the marionette port randomly instead of hardcoding it .
I made a pull request to fix this issue . Please check it out .
If I provide different profile paths to whalesong , the first driver starts just fine , but the subsequent ones show a blank firefox windows . How to fix it ?