Search Issue Tracker
Active
Fixed in 2021.3.32f1, 2022.3.7f1, 2023.1.1f1, 2023.2.0a12
Under Consideration for 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
- Scene is modified after exiting Play Mode when Graphics Compositor is enabled in HD RP
- Shortcuts inconsistently trigger when they have a conflict with the same Command
- On Script import/reimport MonoImporter does not generate consistent results due to updating Custom packages
- [Entities Graphics] Size of the Content Update generated folder increases when changes are made to the Scene
- In Play Mode, an extra Sync Call is made every frame when a GameObject has a Rigidbody 2D component
Add comment