Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.2.X, 2023.1.X
Fixed in 2023.2.0a12
Votes
1
Found in
2020.3.46f1
2021.3.21f1
2022.2.12f1
2023.1.0b9
2023.2.0a8
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
- [Quest 2] Running Entities Graphics/BatchRendererGroup under Vulkan results in a frame rate drop compared to OpenGLES 3 and causes Tile Binning to cost more
- Filters dropdown: Window doesn't rescale on items collapse
- Sprite Preview is broken when the Sprite is too tall or too wide
- Objects are invisible in Scene view when using Wireframe Shading Mode
- Physics.Raycast does not work when used on the whole model
Add comment