Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.46f1
2022.3.53f1
6000.0.29f1
6000.1.0a6
6000.2.0a1
6000.3.0a1
Issue ID
UUM-88911
Regression
No
VRAM usage is constantly increasing when generating procedural textures and building bundles with Vulkan
How to reproduce:
1. Open the “Archive.zip“ project through the CLI with the “-force-vulkan“ argument
2. Open the Task Manager
3. Select the “Texture Creator Settings.asset“ ScriptableObject
4. Change the “Textures“ value to 1000 in the Inspector
5. Start generating textures by clicking on “UnitySupport > Create Textures” in the Toolbar
6. Observe the Task Manager
Additionally:
7. Start building bundles by clicking on “Bundles > Build“ after the generation is done
8. Observe the Task Manager
Expected result: VRAM usage is constant while generating textures and building bundles
Actual result: VRAM usage keeps increasing throughout the texture generation and the bundle-building process
Reproducible in: 2021.3.46f1, 2022.3.531, 6000.0.29f1, 6000.1.0a6
Reproduced on: Windows 11 Pro (23H2), Windows 10 (By the reporter)
Not reproduced on: No other environment tested
Notes:
- Reproducible only with the Vulkan Graphics API
- For almost every texture, there will be a “Vulkan - Suboptimal memory type used for image because of low memory.“ warning displayed after the generation
- After generating textures and building the bundles the memory is released
- With DirectX, GPU usage does not climb over 4 GB usage
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
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
Resolution Note:
There are no fixes planned for this Bug