[Wasm][AOT] The AOT compiler fails silently when running on Windows

[jeromelaban]

Description

The AOT compiler stops working at an unknown location, without any error message.

aot-issue-assets.zip

Here's how to reproduce it:

cd extracted_archive
runtimes\browser-wasm/native/cross/browser-wasm/mono-aot-cross.exe --debug -v  -O=gsharedvt --aot=dedup-skip,llvmonly,asmonly,no-opt,static,direct-icalls,deterministic,nodebug,llvm-path="[...]\emsdk-2.0.23\emsdk/upstream/bin",interp,,depfile=./linker-out/Uno.UI.FluentTheme.dll.depfile,llvm-outfile=./Uno.UI.FluentTheme.dll.bc.tmp .\linker-out\Uno.UI.FluentTheme.dll

With -v, the last two output lines are:

rySingleton__2__Get_2_5287b__959_0_Windows_UI_Xaml_Media_SolidColorBrush
converting llvm method void Uno.UI.FluentTheme.GlobalStaticResources/ResourceDictionarySingleton__2:<Get_2_5288>b__960_0 (Windows.UI.Xaml.Media.SolidColorBrush)
void Uno.UI.FluentTheme.GlobalStaticResources/ResourceDictionarySingleton__2:<Get_2_5288>b__960_0 (Windows.UI.Xaml.Media.SolidColorBrush) emitted as Uno_UI_FluentTheme_Uno_UI_FluentTheme_GlobalStaticResources_ResourceDictionarySingleton__2__Get_2_5288b__960_0_Windows_UI_Xaml_Media_SolidColorBrush
converting llvm method object Uno.UI.FluentTheme.GlobalStaticResources/ResourceDictionarySingleton__2:<get_themeresources_6ae50ee5d890e499f2c9aa02298c937a_ResourceDictionary>b__963_0 (object)

The same command finishes properly when running under linux.

Configuration

6696065

Regression?

Unsure

Other information

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.

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

The AOT compiler stops working at an unknown location, without any error message.

aot-issue-assets.zip

Here's how to reproduce it:

cd extracted_archive
runtimes\browser-wasm/native/cross/browser-wasm/mono-aot-cross.exe --debug -v  -O=gsharedvt --aot=dedup-skip,llvmonly,asmonly,no-opt,static,direct-icalls,deterministic,nodebug,llvm-path="[...]\emsdk-2.0.23\emsdk/upstream/bin",interp,,depfile=./linker-out/Uno.UI.FluentTheme.dll.depfile,llvm-outfile=./Uno.UI.FluentTheme.dll.bc.tmp .\linker-out\Uno.UI.FluentTheme.dll

With -v, the last two output lines are:

rySingleton__2__Get_2_5287b__959_0_Windows_UI_Xaml_Media_SolidColorBrush
converting llvm method void Uno.UI.FluentTheme.GlobalStaticResources/ResourceDictionarySingleton__2:<Get_2_5288>b__960_0 (Windows.UI.Xaml.Media.SolidColorBrush)
void Uno.UI.FluentTheme.GlobalStaticResources/ResourceDictionarySingleton__2:<Get_2_5288>b__960_0 (Windows.UI.Xaml.Media.SolidColorBrush) emitted as Uno_UI_FluentTheme_Uno_UI_FluentTheme_GlobalStaticResources_ResourceDictionarySingleton__2__Get_2_5288b__960_0_Windows_UI_Xaml_Media_SolidColorBrush
converting llvm method object Uno.UI.FluentTheme.GlobalStaticResources/ResourceDictionarySingleton__2:<get_themeresources_6ae50ee5d890e499f2c9aa02298c937a_ResourceDictionary>b__963_0 (object)

The same command finishes properly when running under linux.

Configuration

6696065

Regression?

Unsure

Other information

Author:	jeromelaban
Assignees:	-
Labels:	arch-wasm, untriaged, area-Codegen-AOT-mono
Milestone:	-

[radical]

cc @vargaz @radekdoulik

[radekdoulik]

I have tried to run it with valgrind on linux. No errors, just leaks.

MONO_PATH=linker-out valgrind .../artifacts/bin/mono/Browser.wasm.Release/cross/browser-wasm/mono-aot-cross -O=gsharedvt --aot=dedup-skip,llvmonly,asm
only,no-opt,static,direct-icalls,deterministic,nodebug,llvm-path=".../src/mono/wasm/emsdk/upstream/bin",interp,,depfile=./linker-out/Uno.UI.FluentTheme.dll.depfile,llvm-outfile=./Uno.U
I.FluentTheme.dll.bc.tmp ./linker-out/Uno.UI.FluentTheme.dll
==47864== Memcheck, a memory error detector
==47864== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==47864== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==47864== Command: /home/rodo/wa-main/artifacts/bin/mono/Browser.wasm.Release/cross/browser-wasm/mono-aot-cross -O=gsharedvt --aot=dedup-skip,llvmonly,asmonly,no-opt,static,direct-icalls,deterministic,nodebug,llvm-path=/home/rodo/wa-main/src/mono/wasm/emsdk/upstream/bin,interp,,depfile=./linker-out/Uno.UI.FluentTheme.dll.depfile,llvm-outfile=./Uno.UI.FluentTheme.dll.bc.tmp ./linker-out/Uno.UI.FluentTheme.dll
==47864==
Mono Ahead of Time compiler - compiling assembly /mnt/c/Users/rodo/git/repro/linker-out/Uno.UI.FluentTheme.dll
Compiled: 12703/12703
Output file: '/tmp/mono_aot_X7RNFs'.
Linking symbol: 'mono_aot_module_Uno_UI_FluentTheme_info'.
LLVM output file: './Uno.UI.FluentTheme.dll.bc.tmp'.
JIT time: 145513 ms, Generation time: 34348 ms, Assembly+Link time: 8 ms.
==47864==
==47864== HEAP SUMMARY:
==47864==     in use at exit: 878,549,022 bytes in 8,425,521 blocks
==47864==   total heap usage: 15,594,719 allocs, 7,169,198 frees, 7,687,254,708 bytes allocated
==47864==
==47864== LEAK SUMMARY:
==47864==    definitely lost: 16,538,022 bytes in 267,933 blocks
==47864==    indirectly lost: 38,751 bytes in 922 blocks
==47864==      possibly lost: 352,421,007 bytes in 3,015,908 blocks
==47864==    still reachable: 509,551,242 bytes in 5,140,758 blocks
==47864==                       of which reachable via heuristic:
==47864==                         stdstring          : 270 bytes in 6 blocks
==47864==                         newarray           : 46 bytes in 2 blocks
==47864==         suppressed: 0 bytes in 0 blocks
==47864== Rerun with --leak-check=full to see details of leaked memory
==47864==
==47864== For lists of detected and suppressed errors, rerun with: -s
==47864== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

[jeromelaban]

I forgot to add to this issue, the debugger caught this, when attached:

Unhandled exception at 0x00007FF7D8887021 in mono-aot-cross.exe: 0xC00000FD: Stack overflow (parameters: 0x0000000000000001, 0x00000049D8C03FF8).

I don't have symbols to provide though, as the build does not seem to provide them.

[radekdoulik]

I have opened #57320 for the debug symbols on windows