System Information
Operating system: Linux-5.8.0-25-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.32.00
Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-08 15:12, hash: rB39012146e142 <- Own compile with NanoVDB
Worked: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-08 15:12, hash: rB39012146e142 <- Own compile without NanoVDB
Short description of error
Some days ago I reported a crash bug that got fixed here: https://developer.blender.org/rB6a2a6fa5143e7b115c47b8e2ef4787f569c670df
But I noticed that with my builds it still crashes while the Buildbot builds are stable.
I then recompiled a build without the (still unsuppported?) NanoVDB and it's as stable as the one from the Buildbot. So, is this even a "legal" bug report? If not, just ignore it.
BTW this crash only seem to be happening when a VDB is involved in opposite to the one I reported before where a simple Volume Object would crash Blender. It now also takes a frame change to cause the crash.
Exact steps for others to reproduce the error
- Download and extract the ZIP
- Open the Blend file and press Z + up (or whatever way you prefer to start preview render in the viewport).
- Use the mouse to click around in the timeline to change the current frame. I noticed that when you use the right and left arrow key it's much harder to crash Blender.
- It only crashes with builds using the NanoVDB option, at least as far as I tested it.