Skip to content

Fida Puti Samurai: bounded WOW64 intro-hang stack capture - #29

Open
butilly wants to merge 1 commit into
mainfrom
fix/fida-puti-fexcore-diagnostic
Open

butilly wants to merge 1 commit into
mainfrom
fix/fida-puti-fexcore-diagnostic

Conversation

@butilly

@butilly butilly commented Nov 12, 2026

Copy link
Copy Markdown
Owner

Game: Fida Puti Samurai; executable: Z&L FPS.exe; thread: 1570304916247806022. Unity 2022.3.62f1, 32-bit Mono on Proton 10 ARM64EC and FEX 2512. Player.log ends at play video 0; mfplat tracing yielded no media calls. Latest perf drops to 3-4% game CPU with idle GPU after loading; no crash, manual quick-menu exit. Managed inspection did not distinguish native video setup from completion wait. Existing FEX WOW64 dispatch and logging have no blocked-thread stack trace. Diagnostic round 1 only: adapt the reviewed WOW64 guest int 0x2e sampler entry pattern, scope it to this executable, preserve Proton major and architecture. After 30 seconds take eight cooperative main-thread context samples five seconds apart. Resume before formatting, VM queries or memory reads; record guest/native PCs and module offsets, plus at most sixteen executable-address stack candidates from a bounded 1KB post-resume read per sample. Stack candidates are advisory, not an unwind; validate repeated offsets in the next report. Require sampler-entry and capture-complete markers. No game, media, rendering or JIT semantics are deliberately changed. Source diff whitespace check passed; CI supplies compile/package verification.

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