Search Issue Tracker
Fixed
Fixed in 2022.3.21f1, 2023.2.12f1, 2023.3.0b8
Votes
1
Found in
2022.2.20f1
2023.1.0b17
2023.2.0a16
2023.3.0a3
Issue ID
UUM-35989
Regression
No
LoadRawTextureData takes more time than expected when using TextureCreationFlags.DontUploadUponCreate
Reproduction steps:
1. Open the Superluminal profiler
2. Open the attached "repro_IN-40868.zip" project
3. Start profiling the "Unity.exe" process in the Superluminal profiler
4. Enter the Play Mode in the Unity Editor
5. After a few seconds, stop the Play Mode
6. Stop the profiling in the Superluminal profiler
7. Observe the profiling data
Expected result: no time is spent on Texture2D::UnshareTextureData during LoadRawTextureData, because TextureCreationFlags.DontUploadUponCreate is in use so the TextureData should not be referenced by the upload.
Actual result: the data upload is skipped, but Texture2D::UnshareTextureData still takes longer than expected (RefCount is not 1).
Reproduced with: 2022.2.20f1, 2023.1.0b17, 2023.2.0a16
Could not test with: 2020.3.48f1, 2021.3.25f1 (does not have TextureCreationFlags.DontUploadUponCreate included in the code)
Reproducible on: Windows 10
Note: Reproducible in builds
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
- Shader warning after building a project with URP Sample
- MissingReferenceException after clicking "Fix now" on NormalMap settings
- The "UniversalRenderPipelineGlobalSettings.asset" is creating noise in the git diff when building a Player
- Scene is marked as dirty when opening the project with Vertical Layout Group added as a Component
- Crash on UnityEngine::Animation::SetGenericFloatPropertyValues when keyframing the RigBuilder component to Enabled and Disabled
mgear
Nov 16, 2023 09:18
just a info snippet for unity QA discord:
"Karl Jones: They expect to start work on this bug in December and expect a fix will be available early next year."