Wasn’t me. See if that also happens with the volumeRender SDK demo when you render larger volumes.
I got that error too, but I figured it was due to running the display on a nVidia Quadro 1300FX card and suspected an openGL interoperability bug. I think the leak occurs when the display card is different from the compute card (which the SDK samples choose to always be the highest GFlops CUDA card in the system).
I officially withdraw my stance on the app having a memory leak.
I never did actually receive an ‘out of memory error’.
Just now, I started Voxel Plancton and just let it run for 40 minutes at the default screen…
Nothing odd to report except that the total memory used on the GPU will change from 323MB’s to 324MB’s now and then, but then does return to 323…
After letting it run error free for 40 minutes, I started playing with it some more, and still can’t get the app to crash now. External Image
This is a fun app to mess with. :)
