Search Issue Tracker
Fixed in 2021.1.X
Planned for 2019.4.X, 2020.3.X
Votes
10
Found in
2019.4
2020.1
2020.2
2020.2.0a21
Issue ID
1272396
Regression
No
[CompilationPipeline] Project recompile and package changes takes a long time when Project includes a lot of packages
Reproduction steps:
1. Open the user's attached project, or add attached "manifest.json" file to an empty project
2. Open Window > Analysis > Editor Iteration Profiler
3. Select "Enable" in Editor Iteration Profiler
4. Open Window > Analysis > Compilation Timeline
5. Press "Recompile", this just does a full recompile using CompilationPipeline.RequestScriptCompilation API
Expected result: Recompilation takes less than a minute
Actual result: Logged recompilation takes around a minute after that Editor becomes unresponsive for ~3-4 minutes while maintaining extremely high CPU and RAM usage (~80-90%)
Reproducible with: 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
Couldn't test with: 2018.4 (errors after downgrade)
Note:
1. Using attached "manifest-2019.4.json", Editor freezes upon launch, takes all RAM memory, and needs to be ended using Task Manager - this issue is reported separately as case 1273659
2. Repro project doesn't have any assets but includes a lot of Unity Packages
-
ELenDiL_Unity
Sep 18, 2020 02:23
It also affects third party packages.
Very slow, Import a package like peek takes 40 mins to finish.
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
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a7