Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dead Or Alive 5 (game.exe), Discord thread 1565071668009762856. Follow-up to the memory-query fix at 8cf58ca: report 1565096304965722155 reaches DXVK 2.6.1 swapchain reset, then vkAllocateMemory Exception 0xc0000005 (debug_log L1003) and exit 3 (L1006); the Proton 9 x86_64 comparison also asserts in vkAllocateMemory. The newest supplied report is a separate WineD3D failure, not an allocation trace. Existing WRAPPER_LOG info backend messages begin after memory-type lookup and several fallback conditions; their absence cannot locate the fault conclusively. Preserve the previous fix and all allocation behavior. Add flushed stderr traces for the first 32 requests, bounded pNext metadata, dispatch selection, native-call entry/return and post-allocation bookkeeping completion. No Proton, architecture or feature changes. Next run must identify the last wrapper-alloc marker before the exception, or show successful native return. This is the first allocation diagnostic build. git diff --check passed; CI provides compilation validation.