Errors on Vulkan validation layer
|
After playing for some time I see that it keeps crashing with the FragmentedPoolError, yet the validation layer reports zero errors (using my modified wine). So they are different issues.
|
|
|
Sadly I don't know much about debugging wine or vulkan (you certainly know a lot more than me) xd. But if you need me to test something let me know.
|
|
" Thanks for your offer. Right now I do not have much idea idea of what could be causing the memory problems. There could be memory leaks from poe, from the compilation of the shaders, or somewhere else. And there may be multiple sources of memory leaks, which would complicate matters. Also, having debug activated can sometimes reduce the performance, so you may want to disable them for normal play. This is, unset VK_INSTANCE_LAYERS and perhaps set WINEDEBUG=-all. I had not tell this before, but it is not necessarily obvious. |
|
|
Update about the vk::FragmentedPoolError::FragmentedPoolError: vk::Device::allocateDescriptorSetsUnique error.
It is a mesa error. I have found the bug and patched it in my system. Before the patch I crashed at least once per map. After the patch I have not crashed at all. I have done several Elder guardian maps, plus the Elder himself, plus a little gardening, all without restarting. And since I had changed the driver most shaders had to be recompiled, which is a heavier load than normal. And I had by browser open with a lots of tabs, occupying a lot of memory, which I normally close. The bug is with the memory management of a pool of descriptor sets. The allocated entries shrink when the descriptor set is freed; and after a while, there are no entries able to fit the largest descriptors. So we could call it a very weird memory leak. I have yet to report it upstream. Hopefully they will include the patch soon. The bug affects exclusively vulkan drivers for Intel cards. I will recheck the validation layer another day. |
|
|
I saw that was already merged https://gitlab.freedesktop.org/mesa/mesa/-/commit/b1442e2a6b5cf2116ed1031d76cf20ebd0c7fe6e
I'll test it out to see how it's doing, also good job spotting the problem and reporting :D |
|
