Runtime crashing on startup on emulated x64-on-ARM64 Windows #100425

v-ainigao · 2024-03-14T07:56:51Z

Repro steps:

Install .net9preview3 X64 SDK from https://aka.ms/dotnet/9.0.1xx/daily/dotnet-sdk-win-x64.exe
Modify the environment variable path to x64 "C:\Program Files\dotnet\x64".
Create new console app.
dotnet new console

Expected Result:
Project can be created successfully.

Actual Result:
Creating project or build fails and will be blocking.

dotnet --info
.NET SDK:
Version: 9.0.100-preview.3.24163.23
Commit: 33549194e2
Workload version: 9.0.100-manifests.42eb89a3
MSBuild version: 17.10.0-preview-24162-02+0326fd7c9

Runtime Environment:
OS Name: Windows
OS Version: 10.0.22631
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\x64\sdk\9.0.100-preview.3.24163.23\

.NET workloads installed:
There are no installed workloads to display.

Host:
Version: 9.0.0-preview.3.24162.24
Architecture: x64
Commit: e4fceb3

.NET SDKs installed:
9.0.100-preview.3.24163.23 [C:\Program Files\dotnet\x64\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 9.0.0-preview.3.24162.20 [C:\Program Files\dotnet\x64\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 9.0.0-preview.3.24162.24 [C:\Program Files\dotnet\x64\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 9.0.0-preview.3.24162.12 [C:\Program Files\dotnet\x64\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
arm64 [C:\Program Files\dotnet]
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

The text was updated successfully, but these errors were encountered:

dotnet-issue-labeler · 2024-03-14T07:56:54Z

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

v-ainigao · 2024-03-14T08:02:23Z

Install .net9preview3 X86 SDK create project on Arm64 OS is able to work normally.

richaverma1 · 2024-03-14T15:22:15Z

@v-ainigao is this a regression from .NET9 Preview 2?

marcpopMSFT · 2024-03-14T16:12:18Z

@elinor-fung @agocke since this appears to be a host crash

elinor-fung · 2024-03-14T21:36:50Z

@v-ainigao do you have a dump you could share?

Do other operations - for example dotnet new list, dotnet build, dotnet tool install - work? Does running an app that has already been built work (dotnet <appDll>)?

Since dotnet --info seems to work, this should not be a problem with the host itself.

v-ainigao · 2024-03-15T01:38:15Z

@v-ainigao is this a regression from .NET9 Preview 2?

This issue does not repro with previous versions of net9preview3 and .net9preview2.

v-ainigao · 2024-03-15T02:01:07Z

@v-ainigao do you have a dump you could share?

Do other operations - for example dotnet new list, dotnet build, dotnet tool install - work? Does running an app that has already been built work (dotnet <appDll>)?

Since dotnet --info seems to work, this should not be a problem with the host itself.

This is the latest .net9preview3 x64 SDK from GitHub today running on a newly built ARM64OS.
This memory dump file has been placed in this path. \mlangfs1\public\v-aini#39513dump file.zip
dotnet new console/dotnet new list/dotnet build/dotnet tool install is not working.

Running already built application not working.

But dotnet --info works fine.

elinor-fung · 2024-03-15T23:06:12Z

Running already built application not working.

The screenshot shows dotnet build. Did you also check just running the application? For example dotnet bin\Release\net9.0\a.dll.

This memory dump file has been placed in this path. \mlangfs1\public\v-aini#39513dump file.zip

The main thread is waiting to suspend the runtime for a GC:

00  ARM64EC 0000000d`ca17cf80 00007ffe`14419094     ntdll!#ZwWaitForSingleObject+0x14
01  ARM64EC 0000000d`ca17cf90 00007ffe`1454d4b4     KERNELBASE!WaitForSingleObjectEx+0x84 [minkernel\kernelbase\synch.c @ 1328] 
02  ARM64EC 0000000d`ca17d020 00007ffd`a21ee540     KERNELBASE!$ientry_thunk$cdecl$i8$i8m8i8i8+0x24
03    AMD64 (Inline Function) --------`--------     coreclr!CLREventWaitHelper2+0x6 [D:\a\_work\1\s\src\coreclr\vm\synch.cpp @ 372] 
04    AMD64 0000000d`ca17d0d0 00007ffd`a221a13e     coreclr!CLREventWaitHelper+0x20 [D:\a\_work\1\s\src\coreclr\vm\synch.cpp @ 397] 
05    AMD64 (Inline Function) --------`--------     coreclr!CLREventBase::WaitEx+0xf [D:\a\_work\1\s\src\coreclr\vm\synch.cpp @ 466] 
06    AMD64 (Inline Function) --------`--------     coreclr!CLREventBase::Wait+0xf [D:\a\_work\1\s\src\coreclr\vm\synch.cpp @ 412] 
07    AMD64 0000000d`ca17d130 00007ffd`a2238912     coreclr!ThreadSuspend::SuspendRuntime+0x31e [D:\a\_work\1\s\src\coreclr\vm\threadsuspend.cpp @ 3600] 
08    AMD64 0000000d`ca17d230 00007ffd`a223862a     coreclr!ThreadSuspend::SuspendEE+0x116 [D:\a\_work\1\s\src\coreclr\vm\threadsuspend.cpp @ 5778] 
09    AMD64 0000000d`ca17d310 00007ffd`a2238177     coreclr!GCToEEInterface::SuspendEE+0x26 [D:\a\_work\1\s\src\coreclr\vm\gcenv.ee.cpp @ 51] 
0a    AMD64 0000000d`ca17d340 00007ffd`a22384be     coreclr!WKS::GCHeap::GarbageCollectGeneration+0xf3 [D:\a\_work\1\s\src\coreclr\gc\gc.cpp @ 50661] 
0b    AMD64 0000000d`ca17d390 00007ffd`a22fac8a     coreclr!WKS::gc_heap::trigger_gc_for_alloc+0x26 [D:\a\_work\1\s\src\coreclr\gc\gc.cpp @ 18788] 
0c    AMD64 0000000d`ca17d3c0 00007ffd`a22a99f5     coreclr!WKS::gc_heap::try_allocate_more_space+0x5126e [D:\a\_work\1\s\src\coreclr\gc\gc.cpp @ 18915] 
0d    AMD64 0000000d`ca17d420 00007ffd`a21de818     coreclr!WKS::gc_heap::allocate_more_space+0x31 [D:\a\_work\1\s\src\coreclr\gc\gc.cpp @ 19415] 
0e    AMD64 (Inline Function) --------`--------     coreclr!WKS::gc_heap::allocate+0x5a [D:\a\_work\1\s\src\coreclr\gc\gc.cpp @ 19446] 
0f    AMD64 0000000d`ca17d450 00007ffd`a21c730d     coreclr!WKS::GCHeap::Alloc+0x88 [D:\a\_work\1\s\src\coreclr\gc\gc.cpp @ 49629] 
10    AMD64 (Inline Function) --------`--------     coreclr!Alloc+0xb6 [D:\a\_work\1\s\src\coreclr\vm\gchelpers.cpp @ 227] 
11    AMD64 (Inline Function) --------`--------     coreclr!AllocateObject+0x128 [D:\a\_work\1\s\src\coreclr\vm\gchelpers.cpp @ 1095] 
12    AMD64 (Inline Function) --------`--------     coreclr!AllocateObject+0x12e [D:\a\_work\1\s\src\coreclr\vm\gchelpers.h @ 68] 
13    AMD64 0000000d`ca17d490 00007ffd`a031ef0b     coreclr!JIT_New+0x20d [D:\a\_work\1\s\src\coreclr\vm\jithelpers.cpp @ 2481]

@dotnet/dotnet-diag I can't seem to get sos working for the dump. This is x64 dotnet running on arm64 Windows. The identified target architecture 0xa641 isn't listed as an IMAGE_FILE_MACHINE value - any ideas?

SOS does not support the current target architecture '' (0xa641). A 32 bit target may require a 32 bit debugger or vice versa. In general, try to use the same bitness for the debugger and target process.

mikem8361 · 2024-03-16T00:17:50Z

You must be running on a arm64ec (0xa641). There is already a diagnostic repo issue and a PR that Juan started but still needs some finishing touches to fix this.

v-jieyan2 · 2024-03-19T08:01:04Z

This problem does not appear on winserver 2022.

v-ainigao · 2024-03-21T04:04:33Z

This issue still occurs today on ARM64 win11.
This memory dump file has been placed in this path. \mlangfs1\public\v-aini#39513dump file(2)\dumpfile.zip
CLI version: .net9.0.100-preview.3.24165.20(runtime-9.0.0-preview.3.24162.31)

v-ainigao · 2024-03-27T06:56:54Z

This issue still repro's on .net9.0.100-preview.3.24175.24(runtime-9.0.0-preview.3.24172.9) x64 SDK on ARM64OS.

richaverma1 · 2024-03-27T15:38:19Z

@marcpopMSFT is this blocking .NET 9 Preview 3 release? It is a regression from Preview 2.

marcpopMSFT · 2024-03-27T20:33:18Z

@richaverma1 do other scenarios work (ie build, running an app with dotnet, etc)?

since it's the host crashing and Elinor appears blocked analyzing the dump because of an unrelated issue, not sure how to tell how critical this is without knowing what additional scenarios might be impacted.

CC @baronfel @elinor-fung

marcpopMSFT · 2024-03-27T20:33:40Z

If it's limited to workload installs when running the x64 sdk on an arm64 machine, I wouldn't make it a blocker.

richaverma1 · 2024-03-28T17:32:18Z

@marcpopMSFT it is failing on the basic scenario of creating a console app. But on ARM64 OS with x64 SDK. Not sure how many customers use that config.

v-ainigao · 2024-04-01T06:48:17Z

This issue also repro's on .net9.0.100-preview.4.24181.1(runtime-9.0.0-preview.4.24178.9).

nagilson · 2024-04-01T20:32:27Z

You must be running on a arm64ec (0xa641). There is already a diagnostic repo issue and a PR that Juan started but still needs some finishing touches to fix this.

Thank you for letting us know. Is there any update on that? @mikem8361

mikem8361 · 2024-04-01T20:35:24Z

We haven't had a chance to make any progress on this PR/arm64ec support.

nagilson · 2024-04-01T20:37:27Z

@marcpopMSFT I wouldn't say this is blocking but if it's shipping like this we should probably create a known issue for it.

v-ainigao · 2024-04-10T06:50:33Z

Today I did some sanity checks on the latest .net9preview4[9.0.100-preview.4.24209.11(runtime-9.0.0-preview.4.24204.3)] in CLI. This issue is fixed, so close it.

v-ainigao · 2024-04-16T07:19:44Z

Today I reproduced this issue again on the latest .net9.0.100-preview.4.24215.10(runtime-9.0.0-preview.4.24211.4)x64 SDK on ARM64OS, so I reopened it, can you help me take a look? @marcpopMSFT
This memory dump file has been placed in this path. \mlangfs1\public\v-aini\dump.zip

dotnet --info is well.

v-ainigao · 2024-05-07T03:18:50Z

This issue also repro's on arm64os with .net9preview5 x64sdk.

tommcdon · 2024-05-07T16:03:12Z

I was able to reproduce the issue with an x64 sdk running on Windows arm64. The issue does not reproduce DOTNET_LegacyExceptionHandling=1 so the problem is evidently related to the new EH model. @janvorli would you mind taking a look?

v-ainigao · 2024-05-13T05:22:51Z

This issue still repro's in the latest net9preview4 x64sdk on arm64OS.
SDK version:9.0.100-preview.4.24260.3

janvorli · 2024-05-15T13:05:10Z

Windows developers helped me to investigate the issue. It turns out that it is a windows bug that is fixed in 24H2. So, the recommendation is to update Windows to this version. We will also add a workaround to runtime that will prevent using the Windows API with the bug when running x64 emulated on arm64 Windows on older Windows versions. But please note that this workaround may have some performance consequences in GC runtime suspension time in case of a lot of threads.

v-ainigao · 2024-05-16T01:09:02Z

Windows developers helped me to investigate the issue. It turns out that it is a windows bug that is fixed in 24H2. So, the recommendation is to update Windows to this version. We will also add a workaround to runtime that will prevent using the Windows API with the bug when running x64 emulated on arm64 Windows on older Windows versions. But please note that this workaround may have some performance consequences in GC runtime suspension time in case of a lot of threads.

Thank you for your explanation, but I can't create a 24h2 machine on Azure yet.

In ARM64 windows older than 24H2, the special APC is broken when running x64 emulation. The callback that gets invoked doesn't get an argument with correct CONTEXT of the interrupted location. This change disables using the special APC for runtime suspension when running on the affected Windows versions. Close dotnet#100425

) * Workaround broken special APC when running x64 on arm64 windows In ARM64 windows older than 24H2, the special APC is broken when running x64 emulation. The callback that gets invoked doesn't get an argument with correct CONTEXT of the interrupted location. This change disables using the special APC for runtime suspension when running on the affected Windows versions. Close #100425 * Make the same fix for NativeAOT

v-ainigao · 2024-05-23T07:23:03Z

This issue does not repro in the net9preview5 x64sdk on arm64OS.
SDK version:9.0.100-preview.5.24271.7(runtime-9.0.0-preview.5.24268.2)

…et#102333) * Workaround broken special APC when running x64 on arm64 windows In ARM64 windows older than 24H2, the special APC is broken when running x64 emulation. The callback that gets invoked doesn't get an argument with correct CONTEXT of the interrupted location. This change disables using the special APC for runtime suspension when running on the affected Windows versions. Close dotnet#100425 * Make the same fix for NativeAOT

dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Mar 14, 2024

mikem8361 assigned mikem8361 and unassigned mikem8361 Mar 16, 2024

marcpopMSFT assigned nagilson Mar 26, 2024

dotnet-issue-labeler bot added the area-Setup label Mar 28, 2024

agocke transferred this issue from dotnet/sdk Mar 28, 2024

agocke changed the title ~~[NETSDKE2E][ARM64] Install .net9preview3 X64 SDK create project on Arm64 OS, the system will be blocking.~~ Runtime crashing on startup on emulated x64-on-ARM64 Windows Mar 28, 2024

agocke added area-VM-coreclr and removed area-Setup labels Mar 28, 2024

v-ainigao closed this as completed Apr 10, 2024

dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Apr 10, 2024

v-ainigao reopened this Apr 16, 2024

dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Apr 16, 2024

marcpopMSFT unassigned nagilson Apr 18, 2024

mangod9 added area-ExceptionHandling-coreclr and removed area-VM-coreclr untriaged New issue has not been triaged by the area owner labels May 9, 2024

mangod9 assigned janvorli May 9, 2024

mangod9 added this to the 9.0.0 milestone May 9, 2024

v-ainigao mentioned this issue May 13, 2024

[NETSDKE2E][ARM64].net9preview4sdk can't be used on ARM64OS. #102056

Closed

janvorli mentioned this issue May 16, 2024

Workaround broken special APC when running x64 on arm64 windows #102333

Merged

janvorli closed this as completed in #102333 May 16, 2024

github-actions bot locked and limited conversation to collaborators Jun 22, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Runtime crashing on startup on emulated x64-on-ARM64 Windows #100425

Runtime crashing on startup on emulated x64-on-ARM64 Windows #100425

v-ainigao commented Mar 14, 2024

dotnet-issue-labeler bot commented Mar 14, 2024

v-ainigao commented Mar 14, 2024 •

edited

Loading

richaverma1 commented Mar 14, 2024

marcpopMSFT commented Mar 14, 2024

elinor-fung commented Mar 14, 2024

v-ainigao commented Mar 15, 2024

v-ainigao commented Mar 15, 2024 •

edited

Loading

elinor-fung commented Mar 15, 2024 •

edited

Loading

mikem8361 commented Mar 16, 2024

v-jieyan2 commented Mar 19, 2024 •

edited

Loading

v-ainigao commented Mar 21, 2024 •

edited

Loading

v-ainigao commented Mar 27, 2024

richaverma1 commented Mar 27, 2024

marcpopMSFT commented Mar 27, 2024

marcpopMSFT commented Mar 27, 2024

richaverma1 commented Mar 28, 2024

v-ainigao commented Apr 1, 2024 •

edited

Loading

nagilson commented Apr 1, 2024

mikem8361 commented Apr 1, 2024

nagilson commented Apr 1, 2024

v-ainigao commented Apr 10, 2024

v-ainigao commented Apr 16, 2024

v-ainigao commented May 7, 2024 •

edited

Loading

tommcdon commented May 7, 2024

v-ainigao commented May 13, 2024

janvorli commented May 15, 2024

v-ainigao commented May 16, 2024

v-ainigao commented May 23, 2024

Runtime crashing on startup on emulated x64-on-ARM64 Windows #100425

Runtime crashing on startup on emulated x64-on-ARM64 Windows #100425

Comments

v-ainigao commented Mar 14, 2024

dotnet-issue-labeler bot commented Mar 14, 2024

v-ainigao commented Mar 14, 2024 • edited Loading

richaverma1 commented Mar 14, 2024

marcpopMSFT commented Mar 14, 2024

elinor-fung commented Mar 14, 2024

v-ainigao commented Mar 15, 2024

v-ainigao commented Mar 15, 2024 • edited Loading

elinor-fung commented Mar 15, 2024 • edited Loading

mikem8361 commented Mar 16, 2024

v-jieyan2 commented Mar 19, 2024 • edited Loading

v-ainigao commented Mar 21, 2024 • edited Loading

v-ainigao commented Mar 27, 2024

richaverma1 commented Mar 27, 2024

marcpopMSFT commented Mar 27, 2024

marcpopMSFT commented Mar 27, 2024

richaverma1 commented Mar 28, 2024

v-ainigao commented Apr 1, 2024 • edited Loading

nagilson commented Apr 1, 2024

mikem8361 commented Apr 1, 2024

nagilson commented Apr 1, 2024

v-ainigao commented Apr 10, 2024

v-ainigao commented Apr 16, 2024

v-ainigao commented May 7, 2024 • edited Loading

tommcdon commented May 7, 2024

v-ainigao commented May 13, 2024

janvorli commented May 15, 2024

v-ainigao commented May 16, 2024

v-ainigao commented May 23, 2024

v-ainigao commented Mar 14, 2024 •

edited

Loading

v-ainigao commented Mar 15, 2024 •

edited

Loading

elinor-fung commented Mar 15, 2024 •

edited

Loading

v-jieyan2 commented Mar 19, 2024 •

edited

Loading

v-ainigao commented Mar 21, 2024 •

edited

Loading

v-ainigao commented Apr 1, 2024 •

edited

Loading

v-ainigao commented May 7, 2024 •

edited

Loading