-
Notifications
You must be signed in to change notification settings - Fork 255
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
slang/RHI: nullptr deref in ShaderObjectImpl::writeSamplerDescriptor #5277
Comments
@aleino-nv I'm not able to reproduce this. There's a line in the test to disable wgsl, and I removed that "DISABLE" line, but the test still runs fine (no segfault). Is the issue still present at TOT for you? tests/bugs/user-attribute-lookup.slang |
@cheneym2 Yeah, I'm still seeing the same issue with this test on 79056cd.
|
Oh, nevermind. I was bit again by #5462. I'm able to see the crash now that I have the wgsl backend running correctly again in my new branch. Sorry about that. |
Looks like the user defined attribute is not relevant to the repro, rather it's having a In the test snippet,
The bug can be reproduced replacing all that with just
And then independent of which of the two SamplerState declarations you use, the following additional line fixes the crash:
|
Is it legal to declare the SamplerState object without providing slang-test corresponding input data? I might just do a null check right where there's the segfault in the wgpu rhi backend. It causes the test to fail gracefully(?) with the following validation spew.
The above seems like an improvement over crashing. Then the test passes altogether if I add this line:
|
For most targets, this will be illegal. Let's modify the test to provide the TEST_INPUT line and close this. |
Will do, thanks! |
This makes tests/bugs/shadowed-lookup.slang pass on WGPU. The underlying issue seems similar to shader-slang#5277.
This makes tests/bugs/shadowed-lookup.slang pass on WGPU. The underlying issue seems similar to #5277.
Affected tests:
sampler
isnullptr
for some reason:The text was updated successfully, but these errors were encountered: