Search Issue Tracker
Fixed
Fixed in 2021.3.19f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
Votes
0
Found in
2021.3.16f1
2022.2.2f1
2023.1.0a24
2023.2.0a1
Issue ID
UUM-21771
Regression
Yes
Unnecessary amounts of warnings are logged when using Graphics.CopyTexture()
How to reproduce:
1. Open the user-attached “CopyTextureSpamBugRepro.zip” project
2. Open the “SampleScene” Scene
3. Enter Play Mode
4. Open the Console window
Expected result: Small (~50) and or no amount of “Graphics.CopyTexture called on texture…“ warnings being logged
Actual result: Abyssmal amount of “Graphics.CopyTexture called on texture…“ warnings are being spammed (~2000+)
Reproducible with: 2021.2.0a1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a24
Not reproducible with: 2020.3.43f1, 2021.1.0a10
Reproduced on: macOS Monterey 12.6 (Intel), Windows 10 (10.0.19044) 64bit
Notes:
- Related Forum Thread: [https://forum.unity.com/threads/how-can-i-get-master-texture-limit-logs-to-stop-spamming.1307874|https://forum.unity.com/threads/how-can-i-get-master-texture-limit-logs-to-stop-spamming.1307874]
- The main issue is that an unnecessary amount of warnings are being spammed which in turn causes performance degradation in builds as a secondary issue
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 2023.1.0b3):
Fixed in: 2023.1.0b3
Resolution Note (fix version 2022.2.6f1):
Fixed in: 2022.2.6f1