GC should never pause threads.

[Gavin-Williams]

This has been a long standing issue with C#. It's about time you take another look at garbage collection. Having threads pause is completely unacceptable. Apparently, the GC can halt the application for over 1 second.

If you need to get rid of GC completely and use a different model that's fine, or fix the GC so that it never pauses. Use some variant of reference counting, or just introduce smart pointers into the language. But you just have to replace the GC. It's no good.

[dotnet-policy-service]

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

[MihuBot]

Possible related and/or duplicate issues:

• Pauseless Garbage Collector (Question) #96213
• [Question] GC pause time is too large for 60 fps #65850

[huoyaoyuan]

#115627 is the centralized thread for discussions around GC pause. As discussed in earlier posts, a near real-time GC can pay significant overhead like read-barrier.

There is already a low latency implementation discussed in the thread.