Skip to content
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

.NET6 -- Fatal error. Internal CLR error. (0x80131506) #99745

Open
Farb opened this issue Mar 14, 2024 · 11 comments
Open

.NET6 -- Fatal error. Internal CLR error. (0x80131506) #99745

Farb opened this issue Mar 14, 2024 · 11 comments
Labels
area-VM-coreclr untriaged New issue has not been triaged by the area owner

Comments

@Farb
Copy link

Farb commented Mar 14, 2024

URL(s)

.net version :

839cdfb
6.0.2

Description

I used .net6 to process some business logics.But I encountered a fatal error.

I write a method that is called "MergeDictionary" and only merges two dictionary.The stacktrace is as following:

   Fatal error. Internal CLR error. (0x80131506)
 -   at System.Collections.Generic.Dictionary`2[[System.__Canon, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.__Canon, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Resize(Int32, Boolean)
 -   at System.Collections.Generic.Dictionary`2[[System.__Canon, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.__Canon, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].TryInsert(System.__Canon, System.__Canon, System.Collections.Generic.InsertionBehavior)
 at MyCustomDictionaryExtensions.MergeDictionary(System.Collections.Generic.Dictionary`2<System.String,System.String>, System.Collections.Generic.Dictionary`2<System.String,System.String>, Boolean)
@mairaw mairaw transferred this issue from dotnet/core Mar 14, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Mar 14, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Mar 14, 2024
@huoyaoyuan huoyaoyuan added area-VM-coreclr and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Mar 14, 2024
@huoyaoyuan
Copy link
Member

Have you tested with latest patch of 6.0? 6.0.28 was released yesterday.
Does the same issue reproduce in 8.0?

@jkotas jkotas added the needs-author-action An issue or pull request that requires more info or actions from the author. label Mar 14, 2024
@Farb
Copy link
Author

Farb commented Mar 14, 2024

@huoyaoyuan I asked the user to try again on the other machines. According to his feedback,Desktop PC is ok,but laptop not.
And my desktop is ok too. I have not tried other version runtimes. The following is his pc configuration:

系统信息
当前日期/时间:2024年3月14日,17:27:40
操作系统:Windows 11 专业版 64 位(10.0,版本 22621)
语言:中文(简体)(区域设置:中文(简体))
系统制造商:MACHENIKE
系统型号:S16C
BIOS: 1.07.04TQLM7
处理器: 12th Gen Intel(R) Core(TM) i9-12900H (20 CPUs), ~2.5GHz
内存:32768MB RAM
页面文件:13908MB 已用,20611MB可用
DirectX版本: DirectX 12
。检查 WHQL 数字签名(C)
DxDiag 10.00.22621.0001 64 位 Unicode Copyright @ Microsoft. All rights reserved.

@dotnet-policy-service dotnet-policy-service bot removed the needs-author-action An issue or pull request that requires more info or actions from the author. label Mar 14, 2024
@huoyaoyuan
Copy link
Member

The .NET version from dotnet --info can produce detailed information.

This may already be fixed by earlier patches, so it's important to update and test with latest patch.

@Farb
Copy link
Author

Farb commented Mar 14, 2024

.Net6 info

\env\dotnet>dotnet --info

Host (useful for support):
  Version: 6.0.2
  Commit:  839cdfb0ec

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.NETCore.App 6.0.2 

And I am letting the user try the lateset version 6.0.28

@jkotas jkotas added the needs-author-action An issue or pull request that requires more info or actions from the author. label Mar 14, 2024
@Farb
Copy link
Author

Farb commented Mar 15, 2024

Same error reproduced in the lastest version 6.0.28.
error. Internal CLR error. (0x80131506)

No other detailed stacktrace info.

@dotnet-policy-service dotnet-policy-service bot removed the needs-author-action An issue or pull request that requires more info or actions from the author. label Mar 15, 2024
@Bykiev
Copy link

Bykiev commented Mar 15, 2024

related issue: #91695

@markholst
Copy link

Please note this has been resolved on .NET 7, and, I believe has been merged into .NET 8.
I have wasted an unbelievable amount of time on this issue until I recently saw this issue under .NET 7.
The linked PR demonstrates setting $ENV:DOTNET_TC_QuickJit = 0 is a suitable work-around.
Can you please ensure this fix is merged back into .NET 6 ASAP.

@huoyaoyuan
Copy link
Member

huoyaoyuan commented May 14, 2024

Can you please ensure this fix is merged back into .NET 6 ASAP.

There's only half year remaining for .NET 6 support from today. Only security issues will be considered at this stage. An issue with viable workaround is very unlikely to be considered.

@markholst
Copy link

I'll be honest, that isn't a viable workaround.
And 6 months of support is a reasonable percentage of the 3 year support period.

@huoyaoyuan
Copy link
Member

It's in the policy at https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core:

During the maintenance support period, .NET releases are updated to mitigate security vulnerabilities, only.

The maintenance support period is the final 6 months of support for any release (STS or LTS). After the maintenance period ends, the release is out of support.

There is always a workaround that is upgrading to the next LTS version.

@markholst
Copy link

Well you'd better close this issue as resolved then

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-VM-coreclr untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

5 participants