[NativeAOT] Ensure that suspending thread priority is not below normal.

[VSadov]

GC could be caused by a low-priority thread.
It would help if the thread that performs the suspension and release of the runtime changes its priority temporarily to Normal.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[jkotas]

Is this NativeAOT-specific problem or is this a problem in regular CoreCLR too?

[VSadov]

CoreClr does this. I think it is good to have in NativeAOT, but not necessarily in 7.0

runtime/src/coreclr/vm/threadsuspend.cpp

Line 3295 in 4da3eae

// If this thread is running at low priority, boost its priority. We remember the old

Tweaking thread priorities is a rare scenario as it often causes unwanted consequences.
Even more rare is when a low-priority thread is the one who triggers GC (statistically it is the one who allocates the most). It is still good to have a precaution against other threads starving the one who tries to do suspend them.

In Workstation GC it is also the thread that does the actual GC.