There was an earlier discussion brought up about this. In the implementation of NoGCRegion for regions, there is a potential of wasted commit if this happens.
Tagging subscribers to this area: @dotnet/gc
See info in area-owners.md if you want to be subscribed.
Issue Details
There was an earlier discussion brought up about this. In the implementation of NoGCRegion for regions, there is a potential of wasted commit if this happens.
StartNoGCRegion -> GarbageCollect -> ... -> should_proceed_for_no_gc -> extend_soh_for_no_gc -> commit some memory.
but then performed a GC, and then
allocate_for_no_gc_after_gc -> extend_soh_for_no_gc -> commit the memory again.
The repeated work is wasteful.
There was an earlier discussion brought up about this. In the implementation of NoGCRegion for regions, there is a potential of wasted commit if this happens.
StartNoGCRegion -> GarbageCollect -> ... -> should_proceed_for_no_gc -> extend_soh_for_no_gc -> commit some memory.
but then performed a GC, and then
allocate_for_no_gc_after_gc -> extend_soh_for_no_gc -> commit the memory again.
The repeated work is wasteful.