.net8 String.IndexOf crash

[dotecxy]

Description

I see in the Eventvwr log

Reproduction Steps

Cannot reproduce

Expected behavior

102602000x8000000000000012792ApplicationDESKTOP-E3AHE85Application: sinsam.exe
CoreCLR Version: 8.0.1124.51707
.NET Version: 8.0.11
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
at System.SR.InternalGetResourceString(System.String)
at System.SR.GetResourceString(System.String)
at System.String.IndexOf(System.String, Int32, Int32, System.StringComparison)
at System.String.IndexOf(System.String)
10000210000x800000000000000012793ApplicationDESKTOP-E3AHE85sinsam.exe24.6.20.667110000coreclr.dll8.0.1124.5170767115e10c000000500000000001c7b0e0x42140x1db5a813d93245aC:\Program Files\sinsam\app\sinsam.exeC:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.11\coreclr.dll8aedc4c4-4035-47c9-8074-fad9f1eeb9f0

Actual behavior

Crash

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

[huoyaoyuan]

The crash is be caused by two issues: an invalid StringComparison is passed to IndexOf causing an exception to be thrown, then access violation happens when trying to load resource string for the exception.

This looks like a general reliability issue and not limited to .NET runtime, because it's unlikely to get non-constant StringComparison used.

[Clockwork-Muse]

Although if you're getting System.AccessViolationException, you absolutely should be crashing to desktop immediately anyways. From a "normal end-user" perspective, no message window will be helpful (they can't do anything about it, and in this particular case the programmer may not have any way to fix it either).

[dotnet-policy-service]

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

[jkotas]

There is not enough information to figure out what might be causing this crash.
 
Could you please configure automatic crash dump collection in registry https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps (use 2: Full dump) to create crash dump next time this happens? Once you have a crash dump, you can share it privately with us by opening issue at https://developercommunity.visualstudio.com/ . It should give us some clues to diagnose this crash.

[dotnet-policy-service]

This issue has been marked needs-author-action and may be missing some important information.