Search Issue Tracker
By Design
Votes
0
Found in
2021.3.21f1
2022.3.12f1
2023.1.0b8
2023.2.0a6
2023.3.0a14
Issue ID
UUM-30482
Regression
No
ComputeShader can't access ByteAddressBuffer
How to reproduce:
1. Download and open the attached project
2. Enter Play mode
3. Observe the console window
Expected outcome: No warnings appear
Actual outcome: "GarbageCollector disposing of ComputeBuffer. Please use ComputeBuffer.Release() or .Dispose() to manually release the buffer. To see the stack trace where the leaked resource was allocated, set the UnsafeUtility LeakDetectionMode to EnabledWithStackTrace." warnings appear
Reproduced with2020.3.46f1, 2021.3.21f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6, 2023.3.0a14
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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Resolution Note:
This is working as designed. The only compute buffer mode that supports GPU write access is the default mode, Immutable. The other modes, Dynamic and SubUpdates, are CPU write-only and GPU read-only. In the case where GPU write access is needed, please use the Immutable mode (default mode).