Search Issue Tracker
Fixed
Fixed in 2021.3.32f1, 2022.3.7f1, 2023.1.1f1, 2023.2.0a12
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment