Visitar URL original
SafeProcessHandle.Unix: fix missing DangerousRelease by tmds · Pull Request #37412 · dotnet/runtime · GitHub
Skip to content

SafeProcessHandle.Unix: fix missing DangerousRelease - #37412

Merged
stephentoub merged 1 commit into
dotnet:masterfrom
tmds:process_handle_refcount
Jun 4, 2020
Merged

stephentoub merged 1 commit into
dotnet:masterfrom
tmds:process_handle_refcount

Conversation

@tmds

@tmds tmds commented Jun 4, 2020

Copy link
Copy Markdown
Member

Because the SafeProcessHandle was not owned, ReleaseHandle was
not called, causing the wrapped SafeWaitHandle to never release
its resources.

Fixes #36661

cc @stephentoub

Because the SafeProcessHandle was not owned, ReleaseHandle was
not called, causing the wrapped SafeWaitHandle to never release
its resources.
@ghost

ghost commented Jun 4, 2020

Copy link
Copy Markdown

Tagging subscribers to this area: @eiriktsarpalis
Notify danmosemsft if you want to be subscribed.

@stephentoub stephentoub left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks!

@stephentoub
stephentoub merged commit 13fbbee into dotnet:master Jun 4, 2020
danmoseley pushed a commit to danmoseley/runtime that referenced this pull request Jun 4, 2020
Because the SafeProcessHandle was not owned, ReleaseHandle was
not called, causing the wrapped SafeWaitHandle to never release
its resources.
danmoseley pushed a commit that referenced this pull request Jun 5, 2020
Because the SafeProcessHandle was not owned, ReleaseHandle was
not called, causing the wrapped SafeWaitHandle to never release
its resources.

Co-authored-by: Tom Deseyn <tom.deseyn@gmail.com>
@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Regression: Memory leak when launching child processes

3 participants