-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[6.0, 7.0] Assert failed in coreclr linux arm: GCHeapUtilities::GetGCHeap()->IsInFrozenSegment(obj) #84393
Comments
Tagging subscribers to this area: @dotnet/gc Issue DetailsError Blob{
"ErrorMessage": "GCHeapUtilities::GetGCHeap()->IsInFrozenSegment(obj)",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
} Reproduction Steps
|
According to offline confirmation from @carlossanlop, this is not a new bug, the staging branch has just been populated with the content of the .NET 6 release branch. It would be great if someone on the @dotnet/gc team could share their thoughts regarding severity of this bug and / or its impact on .NET 7 / 8 in the sense of whether it's something that has since been fixed but not backported or whether it's a previously unseen rare failure we just hit for the first time. |
could be #82414 which I made a fix for in 8.0 (it has existed since forever). it does not affect running normally, only affects object validation which is only for debug builds. |
do we want to do something about this? would blocking ci be a reason to backport? |
probably make sense to port if its now failing more consistently. But looks like it has only a couple of hits so far. @carlossanlop is this causing any issues with 6.0 servicing release? |
Just hit it in a 7.0 PR, so I changed the title:
|
removing blocking-clean-ci as it has not failed in 30 days
|
Error Blob
Reproduction Steps
Libraries Test Run checked coreclr Linux arm Release
Report
Summary
Known issue validation
Build: 🔎⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.
Result validation:
Validation performed at: 8/1/2023 10:02:52 PM UTC
The text was updated successfully, but these errors were encountered: