Page MenuHome

openvdb.dll EXCEPTION_ACCESS_VIOLATION
Needs Information from User, NormalPublic

Description

System Information
Operating system: Windows 10
Graphics card: 2070

Blender Version
Broken: 2.93.2

Short description of error

Blender crashes when scrubbing the timeline in a scene that has a lot of .VDB volume objects that (100-400 frame ranges) . This crash happens here and there with 2.93, and it happens all the time in 3.0.

The crash happens with 3.0 even with factory defaults so this is definitely related to scrubbing vdb sequences since the crash occurs between frame changes.

Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF8F8E787DA
Module  : openvdb.dll
Thread  : 00002dfc
Writing: P:\.cache\BlenderTemp\BLEND.crash.txt
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF8F8E787DA
Module  : openvdb.dll
Thread  : 0000111c
Writing: P:\.cache\BlenderTemp\BLEND.crash.txt

Exact steps for others to reproduce the error

I can provide a scene, but it is useless without the actual VDB files. And for two reasons I cant provide them for you to repeat. Unfortunately having couple VDB files won't crash Blender you need at least 12-20 large sequences.

  • They are couple hundred gigabytes.
  • They are commercial files.

Exception: I can upload them for you if it is absolutely necessary. I just need you to provide me a secure and large online dropbox.

However, I am providing the crash log and the details. I will also provide more logs as I go since I have been battling these crashes couple hundred times already in less than a week.

The basic steps are

  • Load 20 large VDB sequences
  • Make sure they aree all enabled.
  • Scrub the timeline

Another crash with slightly different trace.

Event Timeline

kursad k (kursadk) updated the task description. (Show Details)
kursad k (kursadk) updated the task description. (Show Details)
kursad k (kursadk) updated the task description. (Show Details)
kursad k (kursadk) updated the task description. (Show Details)
kursad k (kursadk) updated the task description. (Show Details)
kursad k (kursadk) updated the task description. (Show Details)

Another crash with different vdb issues

Stack trace:
blender.exe         :0x00007FF707A1E4B0  <lambda_a11dac69c08c80864ef4e0b5fb12ec17>::operator()
blender.exe         :0x00007FF707A17F00  tbb::interface9::internal::dynamic_grainsize_mode<tbb::interface9::internal::adaptive_mode<tbb::int
blender.exe         :0x00007FF707A29810  tbb::interface9::internal::start_for<tbb::blocked_range<unsigned __int64>,<lambda_a11dac69c08c80864
tbb.dll             :0x00007FF919CE54D0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FF919CE54D0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FF919CE54D0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
blender.exe         :0x00007FF707A213B0  nanovdb::`anonymous namespace'::OpenToNanoVDB<openvdb::v8_0::tree::Tree<openvdb::v8_0::tree::RootNo
blender.exe         :0x00007FF707A134D0  nanovdb::openToNanoVDB<nanovdb::HostBuffer,openvdb::v8_0::tree::Tree<openvdb::v8_0::tree::RootNode<
blender.exe         :0x00007FF707A2B320  ccl::VDBImageLoader::load_metadata
blender.exe         :0x00007FF707991940  ccl::ImageManager::load_image_metadata
blender.exe         :0x00007FF707991AE0  ccl::ImageHandle::metadata
blender.exe         :0x00007FF707974EA0  ccl::Object::compute_volume_step_size
blender.exe         :0x00007FF7079762C0  ccl::ObjectManager::device_update_flags
blender.exe         :0x00007FF70796F380  ccl::Scene::device_update
blender.exe         :0x00007FF707972360  ccl::Scene::update
blender.exe         :0x00007FF707989E20  ccl::Session::update_scene
blender.exe         :0x00007FF707988ED0  ccl::Session::run_gpu
blender.exe         :0x00007FF707988100  ccl::Session::run
blender.exe         :0x00007FF70A360120  ccl::thread::run
blender.exe         :0x00007FF707228710  std::thread::_Invoke<std::tuple<void * __ptr64 (__cdecl*)(void * __ptr64),ccl::thread * __ptr64>,0,
ucrtbase.dll        :0x00007FF936E71430  configthreadlocale
KERNEL32.DLL        :0x00007FF937807020  BaseThreadInitThunk
ntdll.dll           :0x00007FF9396FCEA0  RtlUserThreadStart

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Thu, Jul 22, 7:05 AM

Is it possible to use one large sequence 20x? Also does this happen if you just add these sequences to empty scene?

kursad k (kursadk) added a comment.EditedThu, Jul 22, 5:46 PM

I was able to crash in an empty scene wiith 24 VDB sequences in 3.x especially if Cycles preview render is enabled. Without Cycles it takes couple frame clicks but it seems random.

Here is the video showing it. I am enabling Cycles then clicking on some frame then Blender just disappears to void.

kursad k (kursadk) added a comment.EditedThu, Jul 22, 6:38 PM

Another fun fact. I can render this test scene fine using Cycles in the commandline. It does not crash however trying to render in the UI crashes Blender. There are Vdb related errors again in the log.

Stack trace:
openvdb.dll         :0x00007FF8F8E75240  openvdb::v8_0::points::AttributeSet::Descriptor::operator!=
openvdb.dll         :0x00007FF8F8E47860  openvdb::v8_0::points::AttributeSet::descriptor
openvdb.dll         :0x00007FF8F8EA1530  openvdb::v8_0::points::StringMetaCache::empty
tbb.dll             :0x00007FF90AA4F690  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FF90AA4F690  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FF90AA451B0  tbb::interface7::internal::isolate_within_arena
tbb.dll             :0x00007FF90AA4A470  tbb::task_scheduler_init::terminate
tbb.dll             :0x00007FF90AA4DBD0  tbb::thread_bound_filter::try_process_item
tbb.dll             :0x00007FF90AA4DBD0  tbb::thread_bound_filter::try_process_item

Here is the crash log

any chance you can repro this with a public data set like the cloud set from disney?

@Ray molenkamp (LazyDodo) That does not seem to be an actual VDB sequence.

rats, good point, well it was worth a shot :)

kursad k (kursadk) added a comment.EditedThu, Jul 22, 8:18 PM

@Ray molenkamp (LazyDodo)

No problem.

Bear in mind that this crash is not only about rendering or timeline scrub. It seems to me that at the core the issue is something about view layer updates and VDBs, everything else about it stems from it. If I disable them in the view layer then I get no crashes since the VDBs are not processed anymore.

In fact processing anything that needs viewlayer updates via Python crashes Blender in these setups.

kursad k (kursadk) added a comment.EditedFri, Jul 23, 4:32 AM

@Richard Antalik (ISS), @Ray molenkamp (LazyDodo)

Here is a simpler blend file which I was able to recreate the VDB crashing conditions. It does not use VDB sequences but has couple free VBDs from the net.

This seems to be a different crash (according to the log) than my original report however there might be a connection between this and the original report.

Here is the crash log from this file.

Load the file

Enable Cycles preview in the viewport. I used the left viewport on the screen. (GPU hybrid mode makes the crash quicker as far as I can tell)

Start clicking on random frames on the time line

.blend file with VDBs

@kursad k (kursadk) provided file crashes mostly as soon as it opens, but that is because my GPU runs out of memory (4GB). Can you check what is VRAM usage when crash happens?

kursad k (kursadk) added a comment.EditedFri, Jul 23, 6:09 PM

This is what I am seeing when I open the scene in 3.x.

I would really expect higher usage, unless that is a limit of integrated GPU perhaps. Can you click in Blender on Help > Save System Info and upload saved file?