[NativeAOT] Initialize GC threshold much earlier #10488
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The threshold value is used by the global reference creation routine to determine whether to start GC collection:
However, the threshold value was being initialized after we've already invoked some non-trivial managed code in the managed NativeAOT runtime, too late to avoid at least a handful of
System.GC.Collect ()
calls:Fix this by splitting the GC threshold value initialization into a separate method which is invoked as soon as possible from the
JNI_OnLoad
function exported by the NativeAOT application.