Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.4f1
2022.1
Issue ID
1385669
Regression
No
[Linux][Vulkan] Editor crashes due to memory leak when building AssetBundles
Reproduction steps:
1. Download and open the attached project: "1140446ExcessiveVramUseOnBundlUnityProject.zip"
2. Go to Bundles > Build
Expected result: The AssetBundle is built without issue
Actual result: The Editor crashes silently due to excessive VRAM usage
Reproducible with: 2020.3.25f1, 2021.2.7f1, 2022.1.0b2
Could not test with: 2019.4.34f1 (Due to errors when opening the project)
Notes:
- Tested on Ubuntu 18.04 with Nvidia GTX 1060 6GB VRAM and Ubuntu 20.04 with Radeon Pro WX 5100 8GB VRAM
- The system with an AMD GPU reproduced the crash consistently, while the one with an Nvidia GPU only sometimes
- GPU usage was monitored by running terminal commands "watch -d -n 0.5 nvidia-smi" when using an Nvidia GPU or "radeontop" when using an AMD GPU
- Building the AssetBundle would sometimes result in a system-wide slowdown (on the system with an Nvidia GPU when the crash wouldn't occur)
- On average, building the AssetBundle would consume around 4.3GB of VRAM by itself (when the crash wouldn't occur)
- Not reproducible with OpenGL Graphics API
- Not reproducible on Windows with either D3D12 or Vulkan
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note (fix version 2022.2):
Fixed in version 2022.2.0a9
Resolution Note (fix version 2022.1):
Fixed in version 2022.1.0b15
Resolution Note (fix version 2021.3):
Fixed in version 2021.3.1f1