http://bugs.winehq.org/show_bug.cgi?id=60215 --- Comment #3 from Aydar Kamaltdinov <aydar.kamaltdinov@gmail.com> --- Reproduced again with `WINEDEBUG=warn+all,err+all` and `WINEESYNC=1` as requested — full log attached (thief_wine_debug_full_crash_2026-08-22.log). Notable: this crash is at a *different* fault address than the one in the original report — `Shipping-ThiefGame.exe+0x11F2A9` this time vs `+0x11F9D9` previously — but the backtrace has the same overall shape (same offset ranges throughout: 0x6F0xxx, 0x109xxxx, 0x10Dxxxx, 0x4A1xxx/0x4A8xxx/0x4AAxxx, 0x11Cxxx, 0x3A9xxx, 0x352xxx, 0x871xxx/0x875xxx). Both are 100% reproducible at their own respective address across repeated runs, but differ from each other run-to-run in what looks like a small, non-deterministic way. This suggests it's not one single isolated null-check bug, but a whole class of similarly-shaped call sites that all assume a sync-object handle is valid. Also much clearer evidence of resource exhaustion this time — right after the crash, cascading `STATUS_INSUFFICIENT_RESOURCES` (c000011f) failures on completely unrelated operations: loading `steam.dll`, writing the engine's own crash dump (`Thief64_4158_2026.08.22-15.24.33.dmp`), and saving `ThiefEngine.ini`. All consistent with the process being genuinely out of file descriptors at that point, not just the one eventfd allocation that happened to matter. Confirmed reproduction on a second, different physical device (Snapdragon 8 Elite Gen 5, less extensively tested than the original Snapdragon 8 Elite device, but same crash behavior observed) — not specific to one SoC/device. Re: testing an old shared-wow64 build vs the new one (per bug 59897) — haven't tried this yet, happy to if you think it'd help narrow things down; let me know which build/version would be most useful to test. Side note, possibly useful, possibly a separate issue: with WINEESYNC=0 (or WINEFSYNC=1 as an alternative), the crash disappears but framerate drops from a stable 60fps to a hard 30fps — GPU-driver/DXVK-version independent, tried several combinations. Haven't dug into why yet; mentioning in case it's a known tradeoff or points at something else in the sync fallback path. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.