Remove invalid GCPROTECT for duplicate slot

[AaronRobinsonMSFT]

Fixes #100739

/cc @janvorli @dotnet/interop-contrib

[AaronRobinsonMSFT]

/azp list

[azure-pipelines]

CI/CD Pipelines for this repository:

• runtime-coreclr outerloop
• runtime-coreclr jitstress
• runtime-coreclr jitstressregs
• runtime-coreclr jitstress2-jitstressregs
• runtime-coreclr gcstress0x3-gcstress0xc
• runtime-coreclr gcstress-extra
• runtime-coreclr r2r-extra
• runtime-coreclr jitstress-isas-x86
• runtime-coreclr jitstress-isas-arm
• runtime-coreclr jitstressregs-x86
• runtime-coreclr libraries-jitstressregs
• runtime-coreclr libraries-jitstress2-jitstressregs
• runtime-coreclr r2r
• runtime-coreclr runincontext
• runtime-coreclr crossgen2
• runtime-libraries-coreclr outerloop
• runtime-libraries-coreclr outerloop-windows
• runtime-libraries-coreclr outerloop-linux
• runtime-libraries-coreclr outerloop-osx
• runtime
• runtime-libraries enterprise-linux
• runtime-libraries stress-http
• runtime-libraries stress-ssl
• runtime-dev-innerloop
• runtime-coreclr crossgen2 outerloop
• coreclr-release-outerloop-nightly
• runtime-coreclr crossgen2-composite
• runtime-jit-experimental
• runtime-coreclr libraries-jitstress
• dotnet-linker-tests
• runtime-coreclr ilasm
• runtime-coreclr crossgen2-composite gcstress
• runtime-staging
• runtime-coreclr pgo
• runtime-coreclr libraries-pgo
• Antigen
• runtime-community
• Fuzzlyn
• runtime-coreclr superpmi-replay
• runtime-wasm
• runtime-coreclr superpmi-diffs
• runtime-coreclr superpmi-asmdiffs-checked-release
• runtime-extra-platforms
• jit-cfg
• runtime-wasm-perf
• runtime-llvm
• runtime-coreclr jitstress-random
• runtime-coreclr libraries-jitstress-random
• runtime-android-grpc-client-tests
• runtime-wasm-libtests
• runtime-wasm-non-libtests
• runtime-android
• runtime-androidemulator
• runtime-ioslike
• runtime-ioslikesimulator
• runtime-linuxbionic
• runtime-maccatalyst
• runtime-coreclr pgostress
• runtime-coreclr jitstress-isas-avx512
• runtime-tools-tests
• runtime-libraries-mono outerloop
• runtime-sanitized
• runtime-wasm-dbgtests
• runtime-wasm-optional
• runtime-ioslike-coreclr
• runtime-ioslike-mono
• runtime-nativeaot-outerloop

[AaronRobinsonMSFT]

/azp run runtime-coreclr gcstress0x3-gcstress0xc

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[AaronRobinsonMSFT]

Failure - #94390

[elinor-fung]

/backport to release/staging-8.0

[github-actions]

Started backporting to release/staging-8.0: https://github.com/dotnet/runtime/actions/runs/15887123907

[github-actions]

@elinor-fung an error occurred while backporting to "release/staging-8.0", please check the run log for details!

Error: The specified backport target branch "release/staging-8.0" wasn't found in the repo.

[elinor-fung]

/backport to release/8.0-staging

[github-actions]

Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/15887172637

[janvorli]

Do we ever run the test with some GC stress mode? I've added detection of double reporting that's enabled when GC stress is enabled (Or it can be enabled manually by DOTNET_CheckDoubleReporting=1). So I wonder if the double reporting didn't work for this case for some reason or if we just don't run that test with GC stress.

[AaronRobinsonMSFT]

So I wonder if the double reporting didn't work for this case for some reason or if we just don't run that test with GC stress.

This testing wasn't running. When I did force it to run under GC Stress, the infrastructure that you did mention caught it. This code path is executed in tests that aren't GC Stress compatible due to how long they run.

[elinor-fung]

Wasn't the original issue reported via a GC stress run for Interop/COM/NativeClients/MiscTypes (that does still appear to be run in GC stress runs)? Or am I missing something.

[AaronRobinsonMSFT]

Wasn't the original issue reported via a GC stress run for Interop/COM/NativeClients/MiscTypes (that does still appear to be run in GC stress runs)? Or am I missing something.

You're right. I specifically remember a converstion directly or indirectly with JanV about his detection of double reporting. It is possible I'm misremembering whether it was during my investigation or after, but I do know the detection system was discussed around the time I put up the PR.