Fix: SeleniumScrapingTool initializes Chrome WebDriver only when needed #230
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix: SeleniumScrapingTool initializes Chrome WebDriver only when needed
Fixes #2258. Implements lazy initialization of the Chrome WebDriver in SeleniumScrapingTool to prevent unwanted browser windows and memory leaks.
Changes
SeleniumScrapingTool
to use lazy initialization of the Chrome WebDriver_create_driver_instance
method to handle the lazy initializationclose
method to ensure proper cleanup of resourcesTesting
All tests pass, including a new test specifically for the lazy initialization behavior.
Link to Devin run: https://app.devin.ai/sessions/6ea1874aa8154fec80ec10d2f18b4ebe