Search Issue Tracker
By Design
By Design in 2023.3.X
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
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).
Resolution Note (2023.3.X):
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).