Skip to content
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

[release/0.9] Remove blocking wait on container exit for every exec created #1604

Merged
merged 1 commit into from
Dec 12, 2022

Conversation

kiashok
Copy link
Contributor

@kiashok kiashok commented Dec 12, 2022

This PR is porting fix with commit hash 5fc00c5 from hcsshim/main to hcsshim release/0.9 branch

Commit fixes the memory leak seen in the shim.
It removes creation of channel that waits on container exit for every new exec. Instead, the container wait channel is exposed through WaitChannel() function which callers can use to decide if container has exited or not.

Signed-off-by: Kirtana Ashok [email protected]

@kiashok kiashok requested a review from a team as a code owner December 12, 2022 18:41
Copy link
Contributor

@anmaxvl anmaxvl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I think we could just do git cherry-pick -x <commit-hash>. you'd need to run go mod tidy && go mod vendor in the test directory. I think 0.9.x is still using vendoring in test.

Commit fixes the memory leak seen in the shim.
It removes creation of channel that waits on container exit
for every new exec. Instead, the container wait channel is exposed
through WaitChannel() function which callers can use to decide
if container has exited or not.

Signed-off-by: Kirtana Ashok <[email protected]>
(cherry picked from commit 5fc00c5)
Signed-off-by: Kirtana Ashok <[email protected]>
@kiashok kiashok merged commit 5d5b210 into microsoft:release/0.9 Dec 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants