Any known issue with updateDescriptorSet on recent versions? #2398
Unanswered
FilippoLeon
asked this question in
Q&A
Replies: 1 comment
-
The latest version from main seems better, and fixes the problem. It introduces a fragmented pool more frequently, but I guess this is a case i should handle. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to upgrade from the SDK version 1.3.250 to 1.3.296 and I'm running into updateDescriptorSet crashing when "under stress".
This only happens with MVK_CONFIG_USE_METAL_ARGUMENT_BUFFERS enabled.
I'm pretty sure my descriptors are still alive and validation is also not reporting problems.
The crashes are of various nature, example, a bad_access in:
libobjc.A.dylib!objc_msgSend (Unknown Source:0)
libMoltenVK.dylib!MVKMetalArgumentBuffer::setBuffer(id, unsigned long, unsigned int) (Unknown Source:0)
libMoltenVK.dylib!MVKBufferDescriptor::write(MVKDescriptorSetLayoutBinding*, MVKDescriptorSet*, unsigned int, unsigned int, unsigned long, void const*) (Unknown Source:0)
I'm doing some extra validation on my side, and maybe compile the latest MoltenVK version to add more info. In the meantime, is there any known regression or something that changed recently?
Beta Was this translation helpful? Give feedback.
All reactions