Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2022.2.0a16
2023.1.0a3
Issue ID
UUM-7794
Regression
No
Building process gets stuck when trying to build AssetBundles (AssetBundle Browser, Mac, high memory usage)
Reproduction steps:
1. Open the attached project
2. Go to Window > AssetBlundle Browser
3. Go to the Build tab and click on the Build button
4. Wait a few minutes and observe that the process is stuck
Expected result: Editor completes the building
Actual result: the building process gets stuck
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.3f1, 2022.2.0a16
Reproducible on: macOS 12.4 (21F79), Windows 10 (21H2)
Note: when the building is done on Apple Silicon Editor, the Virtual Memory Size is really high (400 GB), but if the Intel Editor is used, the Virtual Memory Size is about 60 GB (user attached screenshot)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
AssetBundle browser is not supported and has been mentioned to have known memory issues. To build AssetBundles a script can call BuildPipeline.BuildAssetBundles() or Addressables can be used.
Resolution Note (2023.1.X):
AssetBundle browser is not supported and has been mentioned to have known memory issues. To build AssetBundles a script can call BuildPipeline.BuildAssetBundles() or Addressables can be used.