Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.4f1
6000.4.0b4
6000.5.0a4
Issue ID
UUM-132673
Regression
No
LockBufferForWrite incorrectly rejects valid writes when GraphicsBuffer size exceeds 32-bit limit due to integer overflow
How to reproduce:
1. Create a new project
2. Create an empty GameObject
3. Import the attached “GraphicsBufferOverflowTest.cs” script
4. Assign the script to the GameObject
5. Enter Play Mode
6. Observe the Console
Actual result: The buffer gets created, but LockBufferForWrite throws a “System.ArgumentOutOfRangeException” error
Expected result: LockBufferForWrite succeeds
Reproducible with: 2023.1.0a3, 6000.0.65f1, 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Reproducible on: MacOS Sequoia 15.7.3 (M1 Max)
Not reproducible on: No other environments tested
Notes:
- Error: “LockBufferForWrite<byte> threw: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.”
- LockBufferForWrite should succeed for any write range that is within the actual buffer bounds
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment