Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.17f1
2021.1
2021.2
2022.1
Issue ID
1365218
Regression
No
Crash on an out of memory error when running Play Mode on Metal MacOS
How to reproduce:
1. Open the user's attached project from "Aurelia.zip"
2. Enter Play Mode
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.24f1, 2021.2.0b14, 2022.1.0a11
Notes:
1. Reproduces on macOS Metal, no repro on Windows
How to avoid the issue:
This issue is caused by calling Texture2D.ReadPixels with a rect that lies outside the valid range of pixel coordinates. As a workaround, make sure the source argument overlaps the (0, 0, width, height) rect of the currently set rendertarget before calling Texture2D.ReadPixels
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
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
- Texture looks point-sampled when Mipmap Streaming is enabled
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a6: Added error checking for negative sizes in ReadPixels, so they will lead to an error message rather than an out-of-memory crash.