Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.1.X, 2020.2.X
Votes
0
Found in
2020.1.0a15
2020.2.0b2
Issue ID
1278110
Regression
Yes
Memory usage spikes to 8 GB causes machines with 8 GB RAM the Editor to freeze when building Creator Kit: FPS
How to reproduce:
1. Open the user's attached "New Unity Project2020.2beta.zip" project
2. Go to File -> Build And Run
3. Open the Task Manager
4. Observe Unity's memory usage in the Task Manager
Expected result: The project builds successfully without any noticeable Unity's memory usage spikes (memory usage is around 2 GB)
Actual result: Unity's memory usage is around 7-8 GB (Based on the user's report build process freezes when compiling shaders in the Creator Kit: FPS)
Reproducible with: 2020.2.0a13, 2020.2.0b3
Not reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.6f1, 2020.2.0a12
Note:
- Tested on Windows OS
- The issue is not reproducible if the Caching Preprocessor property is unchecked in the Player Settings
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a2
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b9
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.11f1