Closed raivolink closed 6 months ago
The problem seems to be related to the Chromium argument --no-sandbox
, but why this started to happen in version 124 is still unclear.
As a temporary workaround the library can be modified so that the keyword Open Available Browser
can be toggled to set/not set --no-sandbox
argument although leaving the argument might have other effects on the automation.
Using the latest Chrome 124.0.6367.79 or Edge 124.0.2478.51 library leaves browser processes running about 75% of runs. Console output:
Code used:
With conda: