http://bugs.winehq.org/show_bug.cgi?id=59651 --- Comment #7 from Bernhard Übelacker <bernhardu@mailbox.org> --- Hello, your patch from comment 6 handles only a value of 0xffffffff, but the test from comment 4 should show also other value show this behaviour. However, using this workaround and WINEDEBUG=+pid,+seh leads here not to a crash, but shows several calls to OutputDebugStringA. The last one showing: "Putting shader 47D8511AACA17C6577A1D8EC27E7A8D1 into cache" This my be a hint our shaders.lmdb is stil not opened correctly, because of the workaround. I wonder if this 0xffffffff is used here as the size of the memory mapping, but the file size stays at the few bytes, it got written initially. And windows increases the file size when the mapped memory gets written. -- 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.