If you're using "background GC" (new default), they are doing GC in multiple steps, by running part of GC work in another thread - there are still parts which r

If you're using "background GC" (new default), they are doing GC in multiple steps, by running part of GC work in another thread - there are still parts which require suspension of managed threads. Here's some more insight: https://devblogs.microsoft.com/premier-developer/understanding-different-gc-modes-with-concurrency-visualizer/ https://devblogs.microsoft.com/premier-developer/understandi...