Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.3.X
Votes
2
Found in
Issue ID
1095709
Regression
No
CheckCyclicAssemblyReferences() takes a long time in projects with many assemblies
UnityEditor.Scripting.ScriptCompilation.EditorCompilation.CheckCyclicAssemblyReferences() takes a very long time when there are many assemblies and complex dependencies. It greatly reduces the iteration time. In our project, modifying a simple .cs file would spend >2 minutes in the "pre-compile" stage of refreshing the scripts.
In addition, it sounds like this step should only happen on .asmdef changes, not on .cs changes.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Ribbon Trail mesh collapses into narrow mesh when Emission "Rate over Time" is set to over 664
- Unity_RunCommand tool Details block has unnecessary empty space below the text in Unity MCP Project Settings window section
- Xcode application path is missing spaces in Build Profiles window
- Non-localized strings "ImagePrompt" and "ReferencePrompt" appear in the UI
- NullReferenceException and empty Build Profiles window when BuildProfileContext.asset contains invalid script reference
Add comment