-
Notifications
You must be signed in to change notification settings - Fork 948
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
Raytracing Tests Failing on AMD GPU #6727
Comments
One stack:
|
was this one crashing with an OOM or a access violation? |
Access violation - it crashed in amdvlk64.dll, but I missed those in the stack |
Nevermind I don't think that would help. |
I wonder if it's trying to read from the vertex buffer (we don't and aren't required to set it), can you attach a program that does this to a debugger and see the address it's trying dereference? It would likely be 0. |
Since AMD's drivers are open source, is it possible to get debug symbols out of them? Knowing where the problem is occurring helps figure out what could be occurring. |
Not the windows ones :) |
Oh, that's annoying. Is it possible to (using a debugger) see at what address the access violation is occurring? |
Yeah, I'll look when I've a minute |
Ah alright, it's first doing
r15 is |
At |
We should probably not expose the ray tracing feature on AMD until this stuff is figured out. |
The following tests are all failing with either a device OOM on bind group creation, or a segfault on both my AMD GPUs
The text was updated successfully, but these errors were encountered: