Skip to content

Test failure: profiler/elt/slowpatheltleave/slowpatheltleave.cmd #115319

Description

@SakeTao

Failed in: runtime-coreclr gcstress-extra 20250504.1

Failed tests:

coreclr windows arm64 Checked gcstress0xc_disabler2r_jitstress2 @ Windows.11.Arm64.Open
    - profiler/elt/slowpatheltleave/slowpatheltleave.cmd

Error message:

 
Assert failure(PID 8060 [0x00001f7c], Thread: 6480 [0x1950]): !CREATE_CHECK_STRING(!"Detected use of a corrupted OBJECTREF. Possible GC hole.")

CORECLR! `Object::ValidateInner'::`1'::catch$13 + 0xDC (0x00007ffe`5de6f968)
CORECLR! CallSettingFrame + 0x68 (0x00007ffe`5d8b3240)
CORECLR! _FrameHandler3::CxxCallCatchBlock + 0x1C0 (0x00007ffe`5ddbc9a0)
<no module>! <no symbol> + 0x0 (0xce0d7ffe`d1fe3168)
    File: D:�_work1ssrccoreclr�mobject.cpp:626
    Image: C:hwC2160A55pCoreRun.exe

Unhandled exception. System.Exception: Profiler tests are expected to contain the text 'PROFILER TEST PASSES' in the console output of the profilee app to indicate a passing test. Usually it is printed from the Shutdown() method of the profiler implementation. This text was not found in the output above. Profilee returned exit code -1073740286.
   at Profiler.Tests.ProfilerTestRunner.FailFastWithMessage(String error)
   at Profiler.Tests.ProfilerTestRunner.Run(String profileePath, String testName, Guid profilerClsid, String profileeArguments, ProfileeOptions profileeOptions, Dictionary`2 envVars, String reverseServerName, Boolean loadAsNotification, Int32 notificationCopies)
   at SlowPathELTTests.SlowPathELTLeave.Main(String[] args)

Return code:      1
Raw output file:      C:hwC2160A55wA79A08F7uploadseltslowpatheltleaveoutput.txt
Raw output:
BEGIN EXECUTION
 "C:hwC2160A55pcorerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  slowpatheltleave.dll 
Profiler path: C:hwC2160A55wA79A08F7eprofilereltslowpatheltleaveProfiler.dll
Profilee STDOUT: Profiler.dll!DllGetClassObject
Profilee STDOUT: Profiler.dll!Profiler::Initialize
Profilee STDOUT: Testing leave hooks
Profilee STDOUT: x=-123 y=-4.3 str=Hello, test!
Profilee STDOUT: SimpleArgsFunc returned Hello from SimpleArgsFunc!
Profilee STDOUT: ss=x=1 d=1
Profilee STDOUT: MixedStructFunc returned x=4 d=1
Profilee STDOUT: ls=x0=0 d0=0 x1=1 d1=1 x2=2 d2=2 x3=3 d3=3
Profilee STDOUT: LargeStructFunc returned 3
Test failed: Profiler tests are expected to contain the text 'PROFILER TEST PASSES' in the console output of the profilee app to indicate a passing test. Usually it is printed from the Shutdown() method of the profiler implementation. This text was not found in the output above. Profilee returned exit code -1073740286.
Expected: 100
Actual: -532462766
END EXECUTION - FAILED
FAILED
Test failed. Trying to see if dump file was created in C:cores since 5/4/2025 10:55:41 PM
Processing C:corescorerun.exe.3560.dmp
Unable to find cdb.exe at C:Program Files (x86)Windows Kits10Debuggers�rm64cdb.exe
Processing C:corescorerun.exe.8060.dmp
Unable to find cdb.exe at C:Program Files (x86)Windows Kits10Debuggers�rm64cdb.exe
Test Harness Exitcode is : 1
To run the test:
Set up CORE_ROOT and run.
> C:hwC2160A55wA79A08F7eprofilerprofiler../elt/slowpatheltleave/slowpatheltleave.cmd

Stack trace:

   at TestLibrary.OutOfProcessTest.RunOutOfProcessTest(String assemblyPath, String testPathPrefix)
   at Program.<<Main>$>g__TestExecutor7|0_8(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)

Activity

  1. dotnet-policy-service commented on May 6, 2025

    @dotnet-policy-service
    Contributor

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

  2. added this to the 10.0.0 milestone on May 6, 2025
  3. removed
    untriagedNew issue has not been triaged by the area owner
    on May 6, 2025
  4. modified the milestones: 10.0.0, 11.0.0 on Jul 7, 2025
  5. mdh1418 commented on Jul 30, 2026

    @mdh1418
    Member

    There aren't any failures in the past month, and I cannot retrieve test artifacts or repro.

  6. locked and limited conversation to collaborators on Aug 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions