Search Issue Tracker


Fixed in 2023.3.0a19

Under Consideration for 2024.1.X



Found in




Issue ID




The Editor becomes unresponsive when generating lighting after changing the Minimum Probe Spacing value



Reproduction steps:
1. Open the attached “repro-project“
2. Open the Assets/Scenes/Colosseum_A/Colosseum_A.unity scene
3. Open the “Probe Volumes“ tab of the Window->Rendering->Lighting window
4. Under the “Probe Placement“ section change the Minimum Probe Spacing value to 0.5
5. Click “Generate Lighting“

Expected result: The Editor successfully generates lighting
Actual result: The Editor becomes unresponsive

Reproducible with: 2023.2.0a21
Could not test with: 2021.3.28f1, 2022.3.4f1, 2023.1.2f1 (Could not downgrade the project)

Reproduced on: Windows 10 Pro


This bug seems like a collection of different issues:
1. The Editor crashes in some Physics code on BV4_ProcessStreamSwizzledNoOrderQ<`anonymous namespace'::LeafFunction_BoxOverlapCB,OBBParamsCB>when performing the steps using Unity 2023.2.0a15
2. The Editor.log file is spammed with the following errors when running out of GPU memory while baking with the GPU lightmapper:
OpenCL Error: 'getNormalsFromLastBounceAndDoValidity.EnqueueNDRangeKernel(params.openCLState, 1, NULL, global_work_size, NULL, 0, NULL, NULL)' returned -4 (CL_MEM_OBJECT_ALLOCATION_FAILURE)!
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_NDRANGE_KERNEL on NVIDIA GeForce RTX 3050 Ti Laptop GPU (Device 0).
OpenCL Error: 'processEmissiveFromBounce.EnqueueNDRangeKernel(params.openCLState, 1, NULL, global_work_size, NULL, 0, NULL, NULL)' returned -4 (CL_MEM_OBJECT_ALLOCATION_FAILURE)!

3. In Editor-prev.log for a stack trace from the physics system crashing
========== OUTPUTTING STACK TRACE ==================

0x00007FFC24BB8843 (Unity) internalABP::BoxManager::prepareData
0x00007FFC24BB6EE7 (Unity) internalABP::ABP::Region_prepareOverlaps
0x00007FFC24BB9E42 (Unity) physx::Bp::BroadPhaseABP::update
0x00007FFC24BA4CAB (Unity) physx::Bp::AABBManager::finalizeUpdate
0x00007FFC24BA9831 (Unity) physx::Bp::FinalizeUpdateTask::runInternal
0x00007FFC24AA4FB2 (Unity) physx::Cm::BaseTask::run
0x00007FFC22D7BD42 (Unity) PhysxJobDispatcher::PhysxJobFunc
0x00007FFC225DE8DD (Unity) ujob_execute_job
0x00007FFC225DD843 (Unity) guest_work_until
0x00007FFC225DF078 (Unity) ujob_execute_one_job
0x00007FFC225DC4ED (Unity) JobQueue::ExecuteOneJob
0x00007FFC228538C5 (Unity) CompletionTask::ProcessAllPhysicsTasks
0x00007FFC2288A6E1 (Unity) PhysicsManager::RunSimulation
0x00007FFC2288E3E8 (Unity) PhysicsManager::Simulate
0x00007FFC228823F1 (Unity) `PhysicsManager::InitializeClass'::`2'::FixedUpdatePhysicsFixedUpdateRegistrator::Forward
0x00007FFC22634217 (Unity) ExecutePlayerLoop
0x00007FFC2263437B (Unity) ExecutePlayerLoop
0x00007FFC2263A53D (Unity) PlayerLoop
0x00007FFC23647C2A (Unity) EditorPlayerLoop::Execute
0x00007FFC2365D5E7 (Unity) PlayerLoopController::InternalUpdateScene
0x00007FFC2365C4B3 (Unity) PlayerLoopController::EnterPlayMode
0x00007FFC2365E101 (Unity) PlayerLoopController::SetIsPlaying
0x00007FFC23658745 (Unity) Application::TickTimer
0x00007FFC23ADC89A (Unity) MainMessageLoop
0x00007FFC23AE1DAD (Unity) UnityMain
0x00007FF655852CDA (Unity) __scrt_common_main_seh
0x00007FFCDC017614 (KERNEL32) BaseThreadInitThunk
0x00007FFCDC3C26A1 (ntdll) RtlUserThreadStart

========== END OF STACKTRACE ===========

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.