[release/7.0] [NativeAOT] Ensure that frozen objects respect the minimum object size #76050
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.
Backport of #76031 to release/7.0
/cc @jkotas @filipnavara
Customer Impact
Intermittent crash during GC in native AOT apps
The crash is triggered by a specific virtual address space layout (one GC segment mapped before native binary and second GC segment mapped after the native compiled binary).
Testing
Default native aot CI run
Risk
Low, the change is specific to native aot compiler.
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.