-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assertion failed: GCHeapUtilities::GetGCHeap()->IsInFrozenSegment(obj) #82252
Comments
Tagging subscribers to this area: @dotnet/gc Issue DetailsPipeline runtime-coreclr gcstress-extra Environment:
Log fragment:
|
just a note before I'm blamed again for "Frozen" 🙂 that this assert is a typical sign of a classic gc hole, it's just that on 64bit platform we 99% hit the "padding is not zero" assert instead. |
This failure is showing up in lots of different platform/architecture/stress combinations in runtime-coreclr libraries-jitstress-random: |
Looks like all configurations, even non-stress configurations, are failing with this assert in the cc @dotnet/jit-contrib |
The failure is in
This is a new test introduced in #81006 along with extensive other changes. @steveharter Can you disable this test ASAP (and any other test that might fail in the libraries-jitstress pipeline)? cc @jkotas |
Tagging subscribers to this area: @dotnet/area-system-reflection Issue DetailsPipeline runtime-coreclr gcstress-extra Environment:
Log fragment:
|
Disable this failing test on CoreCLR. Tracking: dotnet#82252
The code was missing support for allocating RuntimeType objects on frozen heap Fixes dotnet#82252
Pipeline runtime-coreclr gcstress-extra
Configuration:
coreclr linux arm Checked gcstress0xc_zapdisable_heapverify1 @ (Ubuntu.1804.Arm32.Open)Ubuntu.1804.Armarch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-18.04-helix-arm32v7
https://dev.azure.com/dnceng-public/public/_build/results?buildId=174092&view=ms.vss-test-web.build-test-results-tab&runId=3460326&paneView=debug&resultId=112277
Environment:
Log fragment:
The text was updated successfully, but these errors were encountered: