[Issue #38236] Bug: Browser processes not cleaned up after automation tasks#7
Draft
bmendonca3 wants to merge 1 commit intomainfrom
Draft
[Issue #38236] Bug: Browser processes not cleaned up after automation tasks#7bmendonca3 wants to merge 1 commit intomainfrom
bmendonca3 wants to merge 1 commit intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Original Issue
Original Issue Description
Browser automation tasks can leave Chrome renderer processes running after task completion, leading to severe CPU/memory accumulation and overheating over time. The issue requests root-cause lifecycle cleanup when tasks complete, sessions end, and gateway restarts, plus optional idle-timeout auto-stop behavior.
Closes openclaw#38236