Skip to content

[Issue #38236] Bug: Browser processes not cleaned up after automation tasks #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
bmendonca3 wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

[Issue #38236] Bug: Browser processes not cleaned up after automation tasks #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions automation/issue-38236.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Issue 38236 Tracking

- Source issue: https://github.com/openclaw/openclaw/issues/38236
- Title: Bug: Browser processes not cleaned up after automation tasks

## Extracted Description
Browser automation can leave zombie Chrome renderer processes that accumulate CPU/memory usage; issue requests lifecycle cleanup on completion/session end/startup and idle timeout safeguards.
Loading