Failed test: OutOfProcessTest::profiler\unittest\releaseondetach\releaseondetach.cmd Windows x86

Open
#116,600 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
testing-qa

Research direction

Reproduce the failure with the listed Windows x86 build and test commands, then inspect src/tests/profiler/unittest/releaseondetach.cs and src/tests/profiler/common/ProfilerTestRunner.cs. Use the ASAN allocation report and the generated output.txt to trace why the profilee exits before printing the expected pass marker. Done means the releaseondetach test completes successfully with the expected exit code and output.

Written by the indexing model from the issue text.

Description

area-Infrastructure
Description

Test failure accompanied with ASAN Report

Reproduction Steps

-Open x86 VS Dev Command Prompt 17.14.4 preview 1.0
-Clone the repo
-Checkout b21c93c
-cd to project root directory
-.\build clr+libs -rc Debug -lc Release -fsanitize address -arch x86
-src/tests/build.cmd debug x86 /p:LibrariesConfiguration=Release
-src/tests/run.cmd debug x86

Expected behavior

Test pass

Actual behavior

Failed test: OutOfProcessTest::profiler\unittest\releaseondetach\releaseondetach.cmd (profiler\unittest\releaseondetach\releaseondetach.cmd) (profiler.profiler)
==71772==ERROR: AddressSanitizer failed to allocate aligned 0x100000 (1048576) bytes of SizeClassAllocator (error code: 487)
==71772==Dumping process modules:
0x00f10000-0x010ed000 C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\CoreRun.exe
0x65e50000-0x68f04000 C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\coreclr.dll
0x68f10000-0x6992e000 C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll
0x6ee50000-0x6ee65000 C:\Windows\SYSTEM32\VCRUNTIME140.dll
0x73780000-0x73794000 C:\Windows\SYSTEM32\kernel.appcore.dll
0x746e0000-0x748c0000 C:\Windows\SYSTEM32\dbghelp.dll
0x75130000-0x75240000 C:\Windows\System32\ucrtbase.dll
0x75310000-0x753db000 C:\Windows\System32\shcore.dll
0x75450000-0x755a8000 C:\Windows\System32\ole32.dll
0x755e0000-0x755fa000 C:\Windows\System32\win32u.dll
0x75810000-0x75900000 C:\Windows\System32\KERNEL32.DLL
0x75910000-0x75adb000 C:\Windows\System32\USER32.dll
0x75ae0000-0x75b84000 C:\Windows\System32\OLEAUT32.dll
0x75cd0000-0x75d53000 C:\Windows\System32\sechost.dll
0x75d60000-0x75de5000 C:\Windows\System32\msvcp_win.dll
0x76250000-0x76273000 C:\Windows\System32\GDI32.dll
0x76280000-0x76347000 C:\Windows\System32\msvcrt.dll
0x76350000-0x7643d000 C:\Windows\System32\gdi32full.dll
0x766c0000-0x7696e000 C:\Windows\System32\KERNELBASE.dll
0x76980000-0x76c06000 C:\Windows\System32\combase.dll
0x76c80000-0x76d39000 C:\Windows\System32\RPCRT4.dll
0x76da0000-0x76e1e000 C:\Windows\System32\ADVAPI32.dll
0x76e30000-0x76e55000 C:\Windows\System32\IMM32.DLL
0x76e60000-0x76ec9000 C:\Windows\System32\bcryptPrimitives.dll
0x76ee0000-0x7709b000 C:\Windows\SYSTEM32\ntdll.dll
AddressSanitizer: CHECK failed: sanitizer_common.cpp:72 "((0 && "unable to mmap")) != (0)" (0x0, 0x0) (tid=52532)
#0 0x68f571d9 (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x100471d9)
#1 0x68f1cc6e (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1000cc6e)
#2 0x68f14000 (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x10004000)
#3 0x68f1b02e (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1000b02e)
#4 0x68f1a81e (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1000a81e)
#5 0x68f2c8bf (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1001c8bf)
#6 0x68f2a91f (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1001a91f)
#7 0x68f2d733 (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1001d733)
#8 0x68f2a17d (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1001a17d)
#9 0x68f29e23 (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x10019e23)
#10 0x68f2a447 (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1001a447)
#11 0x68f2dc5b (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1001dc5b)
#12 0x68f4cafa (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1003cafa)
#13 0x76a70a94 (C:\Windows\System32\combase.dll+0x100f0a94)
#14 0x76a04a02 (C:\Windows\System32\combase.dll+0x10084a02)
#15 0x76a047ce (C:\Windows\System32\combase.dll+0x100847ce)
#16 0x76a040fe (C:\Windows\System32\combase.dll+0x100840fe)
#17 0x76a03bd9 (C:\Windows\System32\combase.dll+0x10083bd9)
#18 0x6678c12d in FinalizerThread::FinalizerThreadStart(void *) C:\gitP\dotnet\runtime\src\coreclr\vm\finalizerthread.cpp:387
#19 0x68f5bbe5 (C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\clang_rt.asan_dynamic-i386.dll+0x1004bbe5)
#20 0x75825d48 (C:\Windows\System32\KERNEL32.DLL+0x6b815d48)
#21 0x76f4d03a (C:\Windows\SYSTEM32\ntdll.dll+0x4b2ed03a)
#22 0x76f4cfc0 (C:\Windows\SYSTEM32\ntdll.dll+0x4b2ecfc0)

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 1.

at Profiler.Tests.ProfilerTestRunner.FailFastWithMessage(String error) in C:\gitP\dotnet\runtime\src\tests\profiler\common\ProfilerTestRunner.cs:line 185

at Profiler.Tests.ProfilerTestRunner.Run(String profileePath, String testName, Guid profilerClsid, String profileeArguments, ProfileeOptions profileeOptions, Dictionary`2 envVars, String reverseServerName, Boolean loadAsNotification, Int32 notificationCopies) in C:\gitP\dotnet\runtime\src\tests\profiler\common\ProfilerTestRunner.cs:line 131

at Profiler.Tests.ReleaseOnShutdown.Main(String[] args) in C:\gitP\dotnet\runtime\src\tests\profiler\unittest\releaseondetach.cs:line 60

Return code: 1
Raw output file: C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\profiler\unittest\releaseondetach\output.txt
Raw output:
BEGIN EXECUTION

C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\profiler\unittest\releaseondetach>set DOTNETCLI=C:\gitP\dotnet\runtime\dotnet.cmd

C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\profiler\unittest\releaseondetach>set __DOTNET_ADD_32BIT=1

C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\profiler\unittest\releaseondetach>set __DOTNET_PREFERRED_BITNESS=32
"C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\corerun.exe" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true" releaseondetach.dll
Profiler path: C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\profiler\unittest\releaseondetach\Profiler.dll
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 1.
Expected: 100
Actual: -532462766
END EXECUTION - FAILED
FAILED
Test Harness Exitcode is : 1

Regression?

No response

Known Workarounds

No response

Configuration

Windows x64 running x86 native tools developer command prompt 17.14.4 preview 1

Other information

This was built with the sanitizer instrumentation fix for Windows from https://github.com/dotnet/runtime/pull/116166

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.