Failed test: OutOfProcessTest::baseservices\TieredCompilation\BasicTestWithMcj\BasicTestWithMcj.cmd Windows x86 -fsanitize address

[39otsu]

Description

Test failure after building with -fsanitize address

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 -fsanitize address /p:LibrariesConfiguration=Release
-src/tests/run.cmd debug x86

Expected behavior

Tests pass

Actual behavior

Failed test: OutOfProcessTest::baseservices\TieredCompilation\BasicTestWithMcj\BasicTestWithMcj.cmd (baseservices\TieredCompilation\BasicTestWithMcj\BasicTestWithMcj.cmd) (baseservices.baseservices)
A subdirectory or file r2r already exists.
==11900==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING.
This can happen for multiple possible reasons:

1. There is a module in the range of the shadow memory
2. Some binaries are compiled with the Static CRT /MT(d) and some are built
   with the Dynamic CRT /MD(d)
   • this needs to be consistent across all binaries in a process, or ASan may
     try to initialize the runtime twice
3. The function stack may be in the range of the shadow memory. This can
   sometimes be worked around by restarting the computer and trying again
   ==11900==ASan shadow was supposed to be located in the [0x2fff0000-0x3fffffff] range.
   ==11900==Dumping process modules:
   0x00a90000-0x01d1c000 C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\crossgen2\crossgen2.exe
   0x60350000-0x60d6e000 C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.44.35207\bin\HostX86\x86\clang_rt.asan_dynamic-i386.dll
   0x615e0000-0x616c1000 C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\Tests\Core_Root\crossgen2\jitinterface_x86.DLL
   0x6b6b0000-0x6b7d7000 C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
   0x6ee50000-0x6ee65000 C:\Windows\SYSTEM32\VCRUNTIME140.dll
   0x72ed0000-0x72f83000 C:\Windows\SYSTEM32\ucrtbase_clr0400.dll
   0x72f90000-0x72fa5000 C:\Windows\SYSTEM32\VCRUNTIME140_CLR0400.dll
   0x72fb0000-0x7376c000 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
   0x73770000-0x73778000 C:\Windows\SYSTEM32\VERSION.dll
   0x73780000-0x73794000 C:\Windows\SYSTEM32\kernel.appcore.dll
   0x73820000-0x738a8000 C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
   0x746e0000-0x748c0000 C:\Windows\SYSTEM32\dbghelp.dll
   0x748d0000-0x748ea000 C:\Windows\SYSTEM32\bcrypt.dll
   0x74930000-0x74985000 C:\Windows\SYSTEM32\mscoree.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
   0x756e0000-0x75761000 C:\Windows\System32\clbcatq.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
   0x76660000-0x766b4000 C:\Windows\System32\SHLWAPI.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
   Activation Context creation failed. Error: 0x00000002
   Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\baseservices\TieredCompilation\BasicTestWithMcj\r2r\BasicTestWithMcj.dll'. The system cannot find the file specified.

File name: 'C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\baseservices\TieredCompilation\BasicTestWithMcj\r2r\BasicTestWithMcj.dll'

Return code: 1
Raw output file: C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\baseservices\TieredCompilation\BasicTestWithMcj\output.txt
Raw output:
BEGIN EXECUTION

C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\baseservices\TieredCompilation\BasicTestWithMcj>set DOTNETCLI=C:\gitP\dotnet\runtime\dotnet.cmd

C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\baseservices\TieredCompilation\BasicTestWithMcj>set __DOTNET_ADD_32BIT=1

C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\baseservices\TieredCompilation\BasicTestWithMcj>set __DOTNET_PREFERRED_BITNESS=32
call RunBasicTestWithMcj.cmd --runCustomTest C:\gitP\dotnet\runtime\artifacts\tests\coreclr\windows.x86.Debug\baseservices\TieredCompilation\BasicTestWithMcj\ BasicTestWithMcj.dll
Collect profile without R2R, use profile without R2R
Collect profile with R2R, use profile with R2R
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 #116166

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.