Page MenuHome

crash when toggling viewport visibility
Closed, DuplicatePublic


System Information
Operating system: Windows 10
Graphics card: GTX 960

Blender Version
Broken: 2.90.1, 2.91
Worked: 2.83.6

Short description of error
crash when toggling viewport visibility

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

  1. Open the attached file
  1. Change the viewport to Rendered

  1. Toggle on the viewport visibility in particle setting
  1. crash
# Blender 2.90.1, Commit date: 2020-09-23 06:43, Hash 3e85bb34d0d7
bpy.context.space_data.shading.type = 'RENDERED'  # Property
bpy.context.object.modifiers["ParticleSettings"].show_viewport = True  # Property

# backtrace
Exception Record:

Exception Address     : 0x00007FF76C32C568
Exception Module      : blender.exe
Exception Flags       : 0x00000000
Exception Parameters  : 0x2
	Parameters[0] : 0x0000000000000000
	Parameters[1] : 0x000001D80F4B1050

Stack trace:
blender.exe         :0x00007FF76C32C550  ?loadTriangle@?$TriangleMi@$03@avx2@embree@@QEBA?AUTriangle@123@HQEBVScene@3@@Z
blender.exe         :0x00007FF76CA9D1F0  embree::avx::BVHNIntersector1<4,1,1,embree::avx::ArrayIntersector1<embree::avx::TriangleMiIntersect
blender.exe         :0x00007FF76C5D6060  embree::avx2::InstanceIntersector1::intersect
blender.exe         :0x00007FF76C31ED80  embree::avx2::BVHNIntersector1<4,1,0,embree::avx2::ArrayIntersector1<embree::avx2::InstanceIntersec
blender.exe         :0x00007FF76B9D4C80  rtcIntersect1
blender.exe         :0x00007FF76B80A860  ccl::kernel_path_trace
blender.exe         :0x00007FF76B7B6280  ccl::kernel_cpu_avx2_path_trace
blender.exe         :0x00007FF76B4CA700  ccl::CPUDevice::render
blender.exe         :0x00007FF76B4CB590  ccl::CPUDevice::thread_render
blender.exe         :0x00007FF76B4CBA30  ccl::CPUDevice::thread_run
blender.exe         :0x00007FF76B4C60B0  std::_Func_impl_no_alloc<<lambda_d884e08a7877f415f05ce8ffda8f97b4>,void>::_Do_call
blender.exe         :0x00007FF76DA7F520  tbb::internal::function_task<std::function<void __cdecl(void)> >::execute
tbb.dll             :0x00007FFA473137A0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFA473137A0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
blender.exe         :0x00007FF76B23D010  tbb::internal::task_group_base::wait
blender.exe         :0x00007FF76DA7E720  ccl::TaskPool::wait_work
blender.exe         :0x00007FF76B8DBCC0  ccl::Session::run_cpu
blender.exe         :0x00007FF76B8DA620  ccl::Session::run
blender.exe         :0x00007FF76DA831A0  ccl::thread::run
blender.exe         :0x00007FF76B091450  std::thread::_Invoke<std::tuple<void * __ptr64 (__cdecl*)(void * __ptr64),ccl::thread * __ptr64>,0,
ucrtbase.dll        :0x00007FFA65171430  configthreadlocale
KERNEL32.DLL        :0x00007FFA668B6FC0  BaseThreadInitThunk
ntdll.dll           :0x00007FFA6791CEA0  RtlUserThreadStart

Event Timeline

Dalai Felinto (dfelinto) changed the task status from Needs Triage to Needs Information from User.Sep 25 2020, 11:48 AM

Thanks for the report. Unfortunately the scenario described is too time consuming for us to track down, we require the bug reporter to narrow down the problem.

Basically the file attached is too big and likely complex to use to reproduce the issue. (and a tip, if you save as compressed file, you don't need to zip the file afterwards)

Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.