Search Issue Tracker
Fixed
Fixed in 2021.3.36f1, 2022.3.20f1, 6000.0.0b11
Votes
19
Found in
2021.3.31f1
2022.3.10f1
2023.3.0b4
6000.0.0b11
Issue ID
UUM-52219
Regression
No
Memory leak when building AssetBundles
Reproduction steps:
1. Open project “MakeBundleTestOH.zip”
2. Click “Test\MakeBundle” through the Main menu
3. Open the Activity Monitor and observe Memory usage next to Unity
Expected result: the memory does not increase
Actual result: the memory starts increasing until the AssetBundle is built
Reproducible with: 2021.3.31f1, 2022.3.10f1
Not reproducible with: 2023.1.0a20, 2023.1.16f1
Couldn’t test with: 2023.1.0a19, 2023.2.0b12, 2023.3.0a9 (due to compiler errors)
Reproducible on: macOS Ventura 13.2.1 (Intel), Windows 11
Not reproducible on: no other environment tested
Note: Couldn’t find the exact fixed version for the 2023.1 stream due to compiler errors in versions 2023.1.0a1 - 2023.1.0a19
-
mhchoi_unity
Mar 28, 2024 03:23
This issue is not resolved yet. As we tested on 2022.3.20f1, there's still the memory increasing issue on our project. It takes up to 30GB of memory during asset bundle build on our mac machine. When we see the memory profiler, it seems that all of sprites in asset bundle were not released from memory during the whole build process. It didn't work like that on 2019.3.31f1 - Sprites was released from memory right after using it and keep the memory usage below 5GB during the build. We're still waiting for the fix now.
-
sn_coder
Mar 11, 2024 01:33
This is happening on ubuntu-22.04 when running via github actions. I upgraded to 2021.3.36f1 and it hasn't been resolved
-
SZCodeLab
Jan 24, 2024 08:58
Upvote for subscribing to the solving alarm.
-
bagelcode
Jan 17, 2024 08:59
Same issue here.
In version 2019.3.31, building asset bundles used about 4GB of memory,
but in version 2022.3.10, the memory usage increases progressively during asset bundle building, reaching up to 27GB.
Once increased, the memory usage remains high even after the asset bundle build is completed. This issue is critical when doing multiple builds, so it needs to be resolved quickly. -
mhchoi_unity
Dec 20, 2023 08:05
Same here. I've checked on 2022.3.15f1 and confirmed that the issue is not resolved. Our product need to build asset bundles over 3GB, and it consumes almost 30GB of memory on our mac and get crashes finally.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2022.3.20f1):
This should fix a memory leak when enumerating files on OSX. No changes to customer code should be required.