Ascension Launcher crashes immediately on Linux (Wine) - STATUS_BREAKPOINT / stack cookie failure, non-deterministic
System:
- Linux Mint 22.3 (Cinnamon)
- Laptop with hybrid graphics: Intel Iris Xe (ADL GT2) + NVIDIA GeForce RTX 3050 Laptop GPU (Optimus)
- NVIDIA driver 595.71.05
- CPU: Intel i7-12650H (AVX2/SSE4.2 present, not a CPU issue)
- Wine: wine-ge-8-26-x86_64 (community-recommended version)
- Launcher version: 1.0.101, Electron 42.1.0 (from Crashpad annotations)
Problem:
Ascension Launcher.exe starts (shows "running" in Lutris) but never shows a window. After 2-90 seconds (inconsistent timing), the main process (CrBrowserMain) terminates. A Crashpad dump is always generated.
Technical analysis of the crash dump (via minidump parsing):
- Exception code: 0x80000003 (STATUS_BREAKPOINT)
- Always at the same address: Ascension Launcher.exe+0x1E83CD5
- Disassembly at this location shows `call __security_check_cookie` followed by `int3; ud2` on failure - i.e. this is a GS stack-cookie failure (a real stack buffer overflow caught by the compiler's stack protector, not an intentional compatibility check)
- The crash is non-deterministic: with identical settings, it sometimes crashes in 2-3 seconds, other times survives 90+ seconds (race condition)
What I've tried (without lasting success):
Fully clean wine prefix, official installer script (win10, corefonts, dotnet48, vcrun2015 - correct order)
wine-ge-8-26 (the recommended version)
--disable-gpu --use-gl=swiftshader --disable-gpu-compositing --in-process-gpu
WINEDLLOVERRIDES=winevulkan=disabled (blocking wine's Vulkan translation layer)
Forcing dxgi/d3d11/d3d9 to builtin (instead of DXVK native)
LC_ALL=en_US.UTF-8 (system had mixed LANG=en_US + LC_NUMERIC/MONETARY=nl_NL)
Windows version override to win10 (build 18362) - the dotnet48 winetricks verb had silently reset it to Win7/7601 without restoring it
Vulkan restricted to only the NVIDIA GPU (VK_ICD_FILENAMES) + __NV_PRIME_RENDER_OFFLOAD
None of the above eliminates the crash - they only seem to (unreliably) affect how quickly it happens.
Question: Is this a known issue? Is there a way to pin to an older, stable launcher build instead of the "latest"/"latest-v2" bootstrap?