Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.1.0a16
2022.2.0a10
Issue ID
UUM-2558
Regression
Yes
[Win11] Editor crashes on GfxDeviceD3D12Base::UpdateComputeConstantBuffers when running a compute shader with Int64BufferAtomics
How to reproduce:
1. Open the attached project "Int64BufferAtomics.zip"
2. Open Scene "SampleScene"
3. Enter Play Mode
Reproducible with: 2022.1.0a16, 2022.1.0b16, 2022.2.0a10
Not reproducible with: 2019.4.37f1, 2021.3.0f1, 2022.1.0a15
First lines of the stack trace:
0x00007FF7F4175775 (Unity) GfxDeviceD3D12Base::UpdateComputeConstantBuffers
0x00007FF7F5765272 (Unity) GfxDeviceWorker::RunCommand
0x00007FF7F576ABAD (Unity) GfxDeviceWorker::RunExt
0x00007FF7F576ACC8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF7F3E167D7 (Unity) Thread::RunThreadWrapper
0x00007FFE20D854E0 (KERNEL32) BaseThreadInitThunk
0x00007FFE22BA485B (ntdll) RtlUserThreadStart
Note:
1. Only reproducible with Windows11
2. DirectX 12 is needed for the script to run
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Changing "PreWarm" parameters on VFX Graph leads to significant performance drops and freeze
- Player display resolution changes to the native resolution of the monitor when Player becomes unresponsive
- [Quest] Game View is no longer rendered in the HMD if it's hidden in the Editor when using Meta Link
- Unity auto-generates code it can't compile when classes are renamed
- Terrain's "Grass Tint" Color picker has Alpha 0 by default
Resolution Note:
There are no fixes planned for this Bug