Skip to content

dotAGE: scope delayed ARM64EC hang captures to the game process - #33

Open
butilly wants to merge 1 commit into
mainfrom
fix/dotage-fexcore-hang-diagnostic
Open

butilly wants to merge 1 commit into
mainfrom
fix/dotage-fexcore-hang-diagnostic

Conversation

@butilly

@butilly butilly commented Nov 13, 2026

Copy link
Copy Markdown
Owner

Game: dotAGE; executable: dotAge.exe; thread: 1570916491463888946. Latest report 1570937927691927623 has a live pre-menu stall, no unhandled fault or NtTerminateProcess, and exit only through quick_menu. Original Assembly-CSharp.dll restored; local0.age display patch remains active. The 45% process CPU average includes loading: after t=58s dotAge.exe is around 10%, but the profiler switches to libpulseaudio.so at 11-13%, losing game-thread detail. Existing FEX suspension/exception logs cannot initiate a live stack capture. Add diagnostic round 1 only for this executable in ARM64EC: ordinary loader-initialized worker, 60-second delay, three rounds 15 seconds apart, up to 128 current-process threads, cooperative NtSuspendThread/NtGetContextThread, bounded syscall-only stack reads, resume before allocation/logging/mapping queries. Log Wine pid/tid, context, CPU times, module offsets, and clearly labelled candidate return addresses, not an unwound backtrace. No emulator behavior or game data changes; retain Proton 11 ARM64EC. Next run: at least 120 seconds, require sampler-entry and sampler-complete, identify repeated main-thread/module candidates and CPU-time deltas. These source changes are container-scoped diagnostics, not an established hang fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant