Skip to content

Test failure: System.Security.Cryptography.Tests #130441

New issue
New issue
Open
Open
Test failure: System.Security.Cryptography.Tests#130441
Assignees
BrzVlad
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabarea-CodeGen-Interpreter-coreclrblocking-clean-ci-optionalBlocking optional rolling runs
Milestone
12.0.0

Description

@JulieLeeMSFT
JulieLeeMSFT
opened on Jul 9, 2026

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1500206
Build error leg or test failing: System.Security.Cryptography.Tests

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "exit code 139 means SIGSEGV Illegal memory access",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1500206
Error message validated: [Condition(s) not met: "SupportsSha3"]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/9/2026 10:47:37 PM UTC

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1500206
Error message validated: [exit code 139 means SIGSEGV Illegal memory access]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/9/2026 10:52:19 PM UTC

Report

Build Repository Test Pull Request
1661201 dotnet/runtime System.Text.Json.SourceGeneration.Roslyn4.4.Tests.WorkItemExecution #135555
1660282 dotnet/runtime System.Net.Quic.Functional.Tests.WorkItemExecution #136828
1659173 dotnet/runtime System.Net.Http.Functional.Tests.WorkItemExecution #136069
1658360 dotnet/runtime System.Security.Cryptography.Xml.Tests.WorkItemExecution
1655237 dotnet/runtime System.Resources.Extensions.Tests.WorkItemExecution #136670
1646246 dotnet/runtime System.Net.Http.Functional.Tests.WorkItemExecution
1639112 dotnet/runtime System.Security.Cryptography.Pkcs.Tests.WorkItemExecution
1637897 dotnet/runtime System.Net.Http.Functional.Tests.WorkItemExecution
1637459 dotnet/runtime Microsoft.Extensions.Logging.Generators.Roslyn4.8.Tests.WorkItemExecution #135896
1635095 dotnet/runtime System.Reflection.Tests.WorkItemExecution
1631070 dotnet/runtime Microsoft.Extensions.Options.SourceGeneration.Tests.WorkItemExecution
1630719 dotnet/runtime System.Reflection.Tests.WorkItemExecution
1630592 dotnet/runtime ComInterfaceGenerator.Unit.Tests.WorkItemExecution
1629765 dotnet/runtime System.Reflection.Tests.WorkItemExecution
1627529 dotnet/runtime System.Runtime.Numerics.Tests.WorkItemExecution
1623173 dotnet/runtime Microsoft.Extensions.Configuration.Binder.SourceGeneration.Tests.WorkItemExecution

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
2 5 16

Activity

  1. JulieLeeMSFT
    added
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Jul 9, 2026
  2. dotnet-policy-service
    added
    untriagedNew issue has not been triaged by the area owner
    on Jul 9, 2026
  3. github-actions
    added
    area-System.Security
    on Jul 9, 2026
  4. JulieLeeMSFT
    added
    blocking-clean-ci-optionalBlocking optional rolling runs
    on Jul 9, 2026

  5. dotnet-policy-service commented on Jul 9, 2026

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Jul 9, 2026 – with Dotnet Policy Service
    Contributor

    Tagging subscribers to this area: @bartonjs, @vcsjones, @dotnet/area-system-security
    See info in area-owners.md if you want to be subscribed.

  6. vcsjones commented on Jul 9, 2026

    @vcsjones
    vcsjones
    on Jul 9, 2026
    Member

    This is a segfault, it is unlike related to the SHA-3 output, that's just the console log indicating the platform does not support SHA-3. I updated the error message and will see if I can figure out the source of the fault.

  7. vcsjones commented on Jul 10, 2026

    @vcsjones
    vcsjones
    on Jul 10, 2026
    Member

    This is the native stack

    Crashing native thread: 0x49eb
Signal: SIGSEGV (11)

#00 0x1077456a4 MethodTable::Validate()
#01 0x107749d98 Object::ValidateInner(int, int, int)
#02 0x10796482c TGcInfoDecoder<InterpreterGcInfoEncoding>::ReportStackSlotToGC(...)
#03 0x107962378 TGcInfoDecoder<InterpreterGcInfoEncoding>::EnumerateLiveSlots(...)
#04 0x10769ae8c InterpreterCodeManager::EnumGcRefs(...)
#05 0x10786d5dc GcStackCrawlCallBack(CrawlFrame*, void*)
#06 0x10778273c Thread::MakeStackwalkerCallback(...)
#07 0x107782918 Thread::StackWalkFramesEx(...)
#08 0x10778394c Thread::StackWalkFrames(...)
#09 0x1078692cc ScanStackRoots(Thread*, ...)
#10 0x107868e5c GCToEEInterface::GcScanRoots(...)
#11 0x1075aa8f0 WKS::gc_heap::background_mark_phase()
#12 0x1075907f0 WKS::gc_heap::gc1()
#13 0x1075a9bf4 WKS::gc_heap::bgc_thread_function()
#14 0x10786c7cc CreateSuspendableThread(...)::__invoke(void*)
#15 0x1079e36e0 CorUnix::CPalThread::ThreadEntry(void*)
#16 0x19ad1bc08 _pthread_start

    Copilot believes this to be an issue with the interpreter GC

    During background GC, the runtime enumerated the first argument slot of:

    Xunit.Sdk.TestInvoker<TTestCase>.CallTestMethod(object)

    as a direct managed object reference. The slot instead contained the address of another interpreter-stack slot. Debug GC validation followed this extra indirection as though it were an object and eventually passed a managed object address to  MethodTable::Validate , causing  SIGSEGV .

    The dump conclusively identifies the invalid GC root and affected method. It narrows the implementation defect to the interpreter’s shared-generic this handling and argument/root lifetime. The precise operation that changed or represented the slot indirectly is not established from the dump alone.

    The “invalid object” is an interpreter-stack address that points to a valid object reference, whose actual  MethodTable  is also valid. This structured, single-extra-indirection pattern—at the shared-generic  this  slot—is characteristic of incorrect GC metadata or argument representation, not random heap damage.

    MethodTable::Validate  makes the failure resemble heap corruption, but it is validating the wrong address. There is no observed corruption of the actual managed object or its  MethodTable ; the evidence instead indicates an interpreter stack/root-reporting bug.

    I don't see anything indicating that this is related to cryptography's code itself as the actual crash fairly far away from it.

  8. vcsjones
    added
    area-CodeGen-Interpreter-coreclr
    and removed
    area-System.Security
    on Jul 10, 2026

  9. dotnet-policy-service commented on Jul 10, 2026

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Jul 10, 2026 – with Dotnet Policy Service
    Contributor

    Tagging subscribers to this area: @JulieLeeMSFT, @BrzVlad, @janvorli, @kg
    See info in area-owners.md if you want to be subscribed.

  10. JulieLeeMSFT commented on Jul 10, 2026

    @JulieLeeMSFT
    JulieLeeMSFT
    on Jul 10, 2026
    MemberAuthor

    @vitek-karas, PTAL.

  11. vitek-karas commented on Jul 11, 2026

    @vitek-karas
    vitek-karas
    on Jul 11, 2026
    Member

    • Timeline:

      • June 22: Regression introduced by PR #128384.
      • July 1: Build 1489776 passed.
      • July 6/8: The original macOS run in Build 1495257 passed, but its July 8 retry crashed in System.Security.Cryptography.Tests.
      • July 8/9: Build 1500206 reproduced the same crash.
      • Local testing confirms the failure is intermittent: affected commits often pass several complete runs before crashing.

    • Affected configuration: Confirmed on net11.0-osx-Release-arm64-interpmode1-OSX.26.Arm64.Open in runtime-libraries-interpreter. It can affect arbitrary test assemblies because the failure occurs while the interpreter reports GC roots, not in cryptography itself.

    • Most likely culprit: PR #128384, Compile runtime async versions of synchronous task-returning methods. In controlled local reproduction attempts on macOS ARM64:

      • Its parent a438371d passed 13/13 local runs.
      • Its merge commit b426fdf crashed on local run 6 with the exact reported stack:
        MethodTable::Validate -> ReportStackSlotToGC -> EnumerateLiveSlots -> InterpreterCodeManager::EnumGcRefs.

      The PR changed interpreter runtime-async call, return, suspension, stack-liveness, and GC-map handling. The evidence indicates incorrect GC metadata or representation of a shared-generic argument slot. Later candidates #129442 and #129474 were ruled out because local clean-build reproduction attempts on commits predating them still crashed.

    Note

    This investigation summary was generated with GitHub Copilot.

  12. vitek-karas commented on Jul 11, 2026

    @vitek-karas
    vitek-karas
    on Jul 11, 2026
    Member

    The most likely PR which caused this is #128384, so adding both @jakobbotsch and @BrzVlad. We should fix this for 11.

  13. vitek-karas
    added this to the 11.0.0 milestone on Jul 11, 2026
  14. vitek-karas
    removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 11, 2026

  15. BrzVlad commented on Jul 15, 2026

    @BrzVlad
    BrzVlad
    on Jul 15, 2026
    Member

    I tried to reproduce locally but failed. Also the last few builds on the interpreter are green and I remember this suite was crashing with every run at some point. I'm wondering if this was somehow fixed recently.

    The filter for this issue is too broad, so the matches are unrelated to the interpreter.

  16. BrzVlad commented on Jul 22, 2026

    @BrzVlad
    BrzVlad
    on Jul 22, 2026
    Member

    Closing this as it hasn't reproduced since and this issue matches on random crashes from other pipelines, unrelated to interpreter. Will keep an eye open for random crashes in interpreter library pipeline, which I believe still happen occasionally.

  17. BrzVlad
    closed this as completedon Jul 22, 2026
  18. JulieLeeMSFT
    reopened this on Jul 22, 2026

  19. JulieLeeMSFT commented on Jul 22, 2026

    @JulieLeeMSFT
    JulieLeeMSFT
    on Jul 22, 2026
    MemberAuthor

    It failed with the same exit code 139 in the interpreter pipeline. Different test name, but maybe the same rootcause. CC @jakobbotsch, @vitek-karas, @BrzVlad.

    Failed in (1):

    Console Log: Console Log
    Source: runtime-libraries-interpreter / net11.0-osx-Release-arm64-interpmode1-OSX.26.Arm64.Open / System.Text.RegularExpressions.Tests

    Failed tests:

    - net11.0-osx-Release-arm64-interpmode1-OSX.26.Arm64.Open
  - System.Text.RegularExpressions.Tests

    Error Message:

    exit code 139 means SIGSEGV Illegal memory access. Deref invalid pointer, overrunning buffer, stack overflow etc. Core dumped.
  20. BrzVlad
    self-assigned this
    on Jul 22, 2026
  21. BrzVlad
    modified the milestones: 11.0.0, 12.0.0 on Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Known Build ErrorUse this to report build issues in the .NET Helix tabarea-CodeGen-Interpreter-coreclrblocking-clean-ci-optionalBlocking optional rolling runs

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions