Building acceleration structures with sphere build inputs causes a valgrind error

Gaming and Visualization Technologies Visualization OptiX
1

Running the optixSphere sample from the OptiX 8.0 SDK with valgrind --track-origins=yes causes an error about uninitialised values being used:

==62195== Conditional jump or move depends on uninitialised value(s)
==62195==    at 0x265576F9: ??? (in /usr/lib/libnvidia-rtcore.so.545.29.02)
==62195==    by 0x2653C96D: ??? (in /usr/lib/libnvidia-rtcore.so.545.29.02)
==62195==    by 0x2654B415: ??? (in /usr/lib/libnvidia-rtcore.so.545.29.02)
==62195==    by 0x2633B18D: ??? (in /usr/lib/libnvidia-rtcore.so.545.29.02)
==62195==    by 0x2633CCAA: ??? (in /usr/lib/libnvidia-rtcore.so.545.29.02)
==62195==    by 0x229FA5CB: ??? (in /usr/lib/libnvoptix.so.545.29.02)
==62195==    by 0x229F82DE: ??? (in /usr/lib/libnvoptix.so.545.29.02)
==62195==    by 0x11A44A: optixAccelComputeMemoryUsage (optix_stubs.h:489)
==62195==    by 0x118751: main (optixSphere.cpp:183)
==62195==  Uninitialised value was created by a stack allocation
==62195==    at 0x2654B16B: ??? (in /usr/lib/libnvidia-rtcore.so.545.29.02)

Triangle build inputs do not cause such an error.
I don’t know if this is a false-positive or not, but I have the same issue in my own project as well.

2

That’s a known issue and is being worked on as we speak.

1 Like