-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: resource cleanup improvements in session teardown #4831
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.
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
Open
SezginKahraman
wants to merge
1
commit into
livekit:main
Choose a base branch
from
SezginKahraman:fix/resource-cleanup
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡
_close_http_ctxstill creates a new HTTP session just to close itThe PR adds a
session.closedcheck in_close_http_ctxwith the stated goal of "avoid creating a new session just to immediately close it." However, the check is ineffective becauseval()calls the_new_sessionfactory, which athttp_context.py:19creates a newaiohttp.ClientSessionwheneverg_session is None or g_session.closed. The newly created session will never haveclosed == True, so the guard on line 59 never prevents the close.Root Cause
The
_new_sessionclosure (line 17-34) always returns a non-closed session. Wheng_sessionisNone(HTTP was never used during the job) or already closed,val()creates a brand newaiohttp.ClientSessionwith aTCPConnector. The new session's.closedproperty isFalse, so the checkif not session.closedon line 59 passes and the session is closed immediately after creation.Scenario: A job runs without ever calling
http_session(). At shutdown,_close_http_ctx()is called (job_proc_lazy_main.py:367).valis notNone(set by_new_session_ctx()at line 283), soval()is invoked, creating an unnecessaryaiohttp.ClientSessionandTCPConnectorjust to immediately close them.The fix should avoid calling
val()entirely when no session was ever created, or the factory should be modified to not create a session when one doesn't already exist.Impact: Unnecessary resource allocation (TCP connector, HTTP session) during every job shutdown where HTTP was unused. Not a crash, but defeats the stated purpose of the fix.
Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.