Search Issue Tracker
Fixed in 5.4.1
Votes
1
Found in
5.4.0b22
Issue ID
805483
Regression
No
Texture2D.ReadPixels crashes/hangs when reading out of rendertarget bounds
ReadPixels does not guard against trying to read out of render target bounds. What exactly happens depends largely on the graphics API used, some handle it better than others.
Original information (somewhat misleading):
Reproduction steps:
1. Open the attached project
2. Switch to DirectX 11
3. Open the available scene
4. Play scene
5. Stop playback
6. Play scene again
Result: Editor freezes, unable to stop playback. Might crash if attempting stop scene.
Note: Might take a couple of tries to reproduce. Only occurs on a NVIDIA GPU in Dx11 mode
Note: Attempting this with Dx9 throws errors, without any performance problems:
'Trying to read pixel out of bounds, reading (1759, 550, 40, 40) from (984, 615)'
Reproduced with: 5.5.0a1, 5.4.0rc3
Not reproducible: 5.3.5p4, 5.2.3p3
Regression since: 5.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment