-
Notifications
You must be signed in to change notification settings - Fork 207
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
Crash when using CompareFloat
with "new" CPUs.
#5430
Comments
Does NOT crash on Flags:
|
I've reproduced this without Gaffer involved, and reported it as a bug in the OSL project. Will open a PR with a workaround in Gaffer shortly. |
This fix looks reasonable as a workaround - hopefully the underlying bug gets fixed quickly, but it will probably take us long enough to get on a new version that it still makes sense to merge this in the mean time. |
Version: Gaffer 1.2.10.0-linux (e.g. 0.47.0.0-linux)
Third-party tools: None
Third-party modules: None
Description
This bug may be an OSL issue but right now I don't quite know how to decouple it from Gaffer and give the OSL guys something to debug. The test scene is very simple but it does only crash on certain CPUs. Note that setting
GAFFEROSL_USE_BATCHED
to0
fixes this bug, which is why I am currently leaning on it being a OSL issue.Fails on this CPU:
Intel(R) Xeon(R) W-2145
Flags:
Replacing
CompareFloat
with custom OSL (which does the exact same thing) does not crash the scene.Steps to reproduce
CompareFloat
node with inputs from a OSL node sayoutput = time * 0.005
and then link to OSLImage or OSLObject)OSLImage
Debug log
Click to Expand
Scene
The text was updated successfully, but these errors were encountered: