Search Issue Tracker
Fixed in 2021.3.32f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X
Votes
5
Found in
2020.3.46f1
2021.3.21f1
2022.2.12f1
2023.1.0b9
2023.2.0a8
2023.3.0a3
Issue ID
UUM-31722
Regression
No
Memory usage rapidly increases when capturing a GameObject with a Line Renderer Component using Texture2D.ReadPixels
How to reproduce:
1. Open the attached user project “Texture2D Memory Test.zip“
2. Build and Run (File>Build And Run)
3. Press “Capture Start“ in the Build
4. Select “Memory“ in the Profiler window
Expected result: Memory usage slowly rises
Actual result: Memory usage quickly rises
Reproducible with: 2020.3.46f1, 2021.3.21f1, 2022.2.12f1, 2023.1.0b9, 2023.2.0a8
Reproduced on: macOS 13.2.1 (Intel)
Not reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment