Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
1
Found in
2020.3.30f1
Issue ID
UUM-7651
Regression
No
WebGL build has high Memory Allocations when using Asset Bundle Cache and CCD
Reproduction steps:
1. Open the uploaded project
2. Turn on Task Manager
3. Build and Run the project
4. Observe "Memory" in the Task Manager
Expected result: Memory usage stays stable
Actual result: Memory usage has a big spike
Reproducible with: 1.16.19 (2020.3.2f1, 2020.3.30f1)
Notes:
- reproduces on Google Chrome, Microsoft Edge, Vivaldi
- Firefox is affected only by bigger projects
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note:
We have addressed memory usage with Addressables in Unity 2022 with a chance to how the caching is implemented. We're not able to backport this change to 2021.
Resolution Note (2020.3.X):
We have addressed memory usage with Addressables in Unity 2022 with a chance to how the caching is implemented. We're not able to backport this change to 2021.