fix: Move HTTPX client cleanup from agent to browser close #1122
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.
The original original PR (#895) addressed the resource warnings and potential memory leaks by adding HTTPX client cleanup to the agent's closing procedure, it introduced a new issue in multi-agent scenarios.
When one agent closes, it cleans up ALL HTTPX clients in memory, including those being used by other agents in the same context.
Reference Demo
test.py
Fix
This PR moves HTTPX cleanup from agent to browser level to: