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.
Final Fantasy III (3D Remake), FF3_Win32.exe, thread 1568752739259777084. Follow-up to allocation diagnostic: direct-driver VK_ERROR_OUT_OF_DEVICE_MEMORY after 821 seconds at size 3686400, allocs 28575 / frees 24427, while reported game RSS grows from 1126 MB at 120 s to 7280 MB at 720 s and Android available memory stays above 8277 MB. Existing ZINK_DEBUG=mem reports only 253 MB of resource objects; compact reproduces and flushsync crashes at startup. No evidenced allocation-policy fix yet. This is the second/final diagnostic: track successful client allocation handles, remove on FreeMemory, print exact outstanding bytes with memory-type/size-order histogram and live wrapped image/buffer counts every 4096 successful allocations and at first failure. Preserve driver results, memory types, rendering, submission mode and Proton major/arch. Diagnostic data is freed on device teardown; bookkeeping failures are counted. Next run must compare live bytes and object counts through the previous failure window to distinguish retained backing allocations from resource-object growth or driver-internal memory. Diff whitespace check passes; CI compiles the Android package.