Skip to content

Conversation

@markples
Copy link
Contributor

In #105521, the number of regions to be decommitted can be reduced, but the budgets weren't updated to include the new regions. This was fine for huge regions, which just sit in the global free list anyway, and it (sort of) works in release builds (though some regions may end up decommitted anyway if they are still in the surplus list at the end of distribution), but it isn't the intended behavior and can trigger a debug assertion that the surplus list is empty.

This change (a subset of #106168), restructures distribute_free_regions so that instead of "decommit or adjust budgets", we first decommit and adjust the remaining balance. Then we adjust budgets based on the new value.

@markples markples self-assigned this Aug 14, 2024
@ghost ghost added the area-GC-coreclr label Aug 14, 2024
@dotnet-policy-service
Copy link
Contributor

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

@markples markples changed the title [GC} Allow distribute_free_regions to decommit and redistribute [GC] Allow distribute_free_regions to decommit and redistribute Aug 16, 2024
@markples
Copy link
Contributor Author

/ba-g BA isn't seeing that the runtime job is done. The only failure is stackoverflowtester, which BA found as known in a previous run.

@markples markples merged commit 566a3bd into dotnet:main Aug 16, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Sep 16, 2024
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.

2 participants