Search Issue Tracker
Fixed
Fixed in 2023.1.0a11
Votes
0
Found in
2023.1.0a6
Issue ID
UUM-12768
Regression
Yes
Crash in OpenCLBufferWrapperBase::EnqueueReadBuffer after launching GPU lightmapper bake
*Steps to repro:*
1. Open the attached project and "ProgressiveLightmappingExample" scene;
2. In the Lighting window (Window>Rendering>Lighting) press Generate Lighting button.
*Expected result:*
Baking proceeds and finishes as expected.
*Actual result:*
Editor crashes. Following stacktrace is obtained:
0x00007FFE4899D04B (Unity) OpenCLBufferWrapperBase::EnqueueReadBuffer
0x00007FFE4899D0D9 (Unity) AsyncBuffer::EnqueueReadBufferAsync
0x00007FFE48A155C4 (Unity) RadeonRaysJobCompositeLightmap::CompositeLightmap
0x00007FFE489B6C07 (Unity) BakeJobCompositeLightmap::Execute
0x00007FFE48978C69 (Unity) `anonymous namespace'::ProcessJobs
0x00007FFE4897C77A (Unity) BakeContextManager::UpdateFunction
0x00007FFE4896FAF5 (Unity) BakeContextManager::DispatchUpdateFunction
0x00007FFE4755E4C6 (Unity) Thread::RunThreadWrapper
0x00007FFEEDD27034 (KERNEL32) BaseThreadInitThunk
0x00007FFEEDF62651 (ntdll) RtlUserThreadStart
Regression introduced in Version 2023.1.0a5.
See attached video and Editor.log file.
_Notes:_
* Reproducible in Version 2023.1.0a9, 2023.1.0a5;
* Not reproducible in Version 2023.1.0a4, 2022.2.0b6, 2021.3.9f1;
* Reproducible on Windows (NVIDIA GeForce GPU) and macOS (AMD Radeon Pro GPU);
* Reproducible with GPU Lightmapper; not reproducible with CPU Lightmapper.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Add comment