Always keep chromedriver running for faster subsequent startups
Removed the persistent_chrome config flag - chromedriver is now always kept running after webdriver_quit. This eliminates startup latency for subsequent WebDriver sessions. Safaridriver is still killed on quit since it doesn't benefit from persistence in the same way. Updated quit message to correctly indicate chromedriver remains running.
This commit is contained in:
@@ -179,10 +179,6 @@ pub struct WebDriverConfig {
|
||||
pub chromedriver_binary: Option<String>,
|
||||
#[serde(default)]
|
||||
pub browser: WebDriverBrowser,
|
||||
#[serde(default)]
|
||||
/// Keep chromedriver running after session ends for faster subsequent startups
|
||||
/// When true, chromedriver process is not killed on webdriver_quit
|
||||
pub persistent_chrome: bool,
|
||||
}
|
||||
|
||||
impl Default for AgentConfig {
|
||||
|
||||
Reference in New Issue
Block a user