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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment