Page MenuHome

Blender crashes when using Gas Fluid Domain in Cycles
Closed, ResolvedPublic


System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38

Blender Version
Broken: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: rB3e85bb34d0d7
Worked: blender-2.82a-windows64

Short description of error
For some reason, Blender crashes when I'm in Cycles and in Rendered view and I make an object a Fluid of type Domain. This only happens when Domain Type is set to Gas, not Liquid. It happens with both CPU and GPU Compute, so it's not a graphics driver problem.

A 40-second clip of what happens:

Console output:




Someone else on r/blender mentioned that it happens to them too ( They apparently have tested it on both 2.83.7 and the latest 2.91.0 alpha on Linux.

Before the crash the debug log reports warnings and errors:

Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
Error: Program undefined behavior warning: The current GL state uses a sampler (0) that has depth comparisons disabled, with a texture object (0) with a non-depth format, by a shader that samples it with a shadow sampler. Using this state to sample would result in undefined behavior.
Stack trace:
blender.exe         :0x00007FF6ACF8A540  ccl::BVH::pack_primitives
blender.exe         :0x00007FF6ACF89C50  ccl::BVH::refit
blender.exe         :0x00007FF6A9ED92C0  ccl::Geometry::compute_bvh
blender.exe         :0x00007FF6A9EE2980  std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl ccl::Geometry::*)(ccl::Device * 
blender.exe         :0x00007FF6ABF7FE70  tbb::internal::function_task<std::function<void __cdecl(void)> >::execute
tbb.dll             :0x00007FFD911637A0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFD911637A0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
blender.exe         :0x00007FF6A8E91BA0  tbb::internal::task_group_base::wait
blender.exe         :0x00007FF6ABF7F070  ccl::TaskPool::wait_work
blender.exe         :0x00007FF6A9EDA570  ccl::GeometryManager::device_update
blender.exe         :0x00007FF6A9E58450  ccl::Scene::device_update
blender.exe         :0x00007FF6A9E5A100  ccl::Scene::update
blender.exe         :0x00007FF6A9E71170  ccl::Session::update_scene
blender.exe         :0x00007FF6A9E729E0  ccl::Session::run_cpu
blender.exe         :0x00007FF6A9E71340  ccl::Session::run
blender.exe         :0x00007FF6ABF82760  ccl::thread::run
blender.exe         :0x00007FF6A969D710  std::thread::_Invoke<std::tuple<void * __ptr64 (__cdecl*)(void * __ptr64),ccl::thread * __ptr64>,0,
ucrtbase.dll        :0x00007FFDCB261430  configthreadlocale
KERNEL32.DLL        :0x00007FFDCD6C6FC0  BaseThreadInitThunk
ntdll.dll           :0x00007FFDCD99CEA0  RtlUserThreadStart

Exact steps for others to reproduce the error

  1. Switch to the Rendered view
  2. Switch from Eevee to Cycles
  3. Click on the default cube
  4. Go to the Physics Properties tab
  5. Click on Fluid
  6. Change Type to Domain

Event Timeline

Robert Guetzkow (rjg) changed the task status from Needs Triage to Needs Information from User.EditedOct 20 2020, 7:45 PM

Unfortunately, there is no stack trace in your blender.crash.txt, likely because you're using the Steam version that is missing the debug symbols. I also can't reproduce the crash on my system with the lastest master. I can reproduce it, the steps to reproduce the bug had Cycles and Eevee switched.

Could you please download the daily build of Blender 2.91, extract it and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files (debug log and system information). Add the debug log to your bug report by clicking on the upload button as shown in the screenshot below. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\blender.crash.txt which should then contain the stack trace. You can type %TEMP% into the path bar of the Windows Explorer to open the directory.

Yes, I was using the Steam version.

Robert Guetzkow (rjg) changed the task status from Needs Information from User to Needs Triage.Oct 21 2020, 12:23 AM
Richard Antalik (ISS) changed the task status from Needs Triage to Confirmed.Oct 21 2020, 10:56 AM
Richard Antalik (ISS) updated the task description. (Show Details)
Sebastián Barschkis (sebbas) triaged this task as High priority.Oct 21 2020, 10:56 AM

Confirmed and really high priority

Confirmed on 2.83.0 too

Can confirm D9340 fixes the crash. This one is for @Brecht Van Lommel (brecht) to decide though.