-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPU address fault error when using descriptor indexing + variable descriptor count #2278
Comments
I think I ran into the same issue with Metal + SPIRV-Cross recently: |
I'm facing a similar issue: #2271 |
Unfortunately I'm not able to replicate this running your app on M3 macOS 14.6.1 with latest MoltenVK. The following log was generated with these env vars set:
Test program log
|
@giomasce When you say
Does this mean you can work around the issue by passing 0 as the first element in |
Yes, thought I don't really consider it a workaround. You're doing a different thing, that doesn't hit the bug. If you need a push constant to be 1 you cannot replace it with 0. |
Now I have an M3 Max myself too, and I cannot replicate the bug there, using the latest MoltenVK. It still happens on my M2. Both are Sonoma 14.6.1, so there might be something that changed on the GPU. |
FWIW, the GPU address fault also occurs in my renderer on an M1, using SDK 1.3.296.0. Tested on both M1 and M2 Max. Does not occur with SDK 1.3.290.0. |
As my previous issue, this comes from the vkd3d test suite. I converted it to pure Vulkan and made as minimal as possible. On my M2 MacBook Air this program spits out the following error:
The program passes both Vulkan and Metal validation, and I can't see any other mistake that might pass through the Vulkan validator.
Not using variable descriptor counts seem to fix the issue, as does passing zero as the first push constant (which is used to address the descriptor array).
Test program source code
The text was updated successfully, but these errors were encountered: