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

Aggressive GC #69695

Merged
merged 6 commits into from
Jun 1, 2022
Merged

Aggressive GC #69695

merged 6 commits into from
Jun 1, 2022

Conversation

cshung
Copy link
Member

@cshung cshung commented May 23, 2022

Fixes #66037

@dotnet-issue-labeler
Copy link

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

@ghost
Copy link

ghost commented May 23, 2022

Tagging subscribers to this area: @dotnet/gc
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #66037

Author: cshung
Assignees: -
Labels:

area-GC-coreclr, new-api-needs-documentation

Milestone: -

@cshung cshung changed the title [WIP] Aggressive GC Aggressive GC May 24, 2022
src/coreclr/gc/gc.cpp Outdated Show resolved Hide resolved
Copy link
Member

@Maoni0 Maoni0 left a comment

Choose a reason for hiding this comment

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

LGTM!

@cshung cshung merged commit 41c1c10 into dotnet:main Jun 1, 2022
@cshung cshung deleted the public/aggressive-gc branch June 1, 2022 16:22
@ghost ghost locked as resolved and limited conversation to collaborators Jul 1, 2022
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.

[API Proposal]: Let the application author tell us to be idle.
4 participants