Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.2.0f3
Issue ID
962760
Regression
No
Performance degradation in large codebases when AddComponent is used
Steps to reproduce:
1. Open attached project
2. Move the plugins folder out of the project
3. Reimport all assets and reload the editor
4. Play the test scene notice that without the plugins folder CPU usage goes up to 2.8ms
5. Move the plugins folder back into the project, RELOAD THE EDITOR
6. Play the test scene and notice that with the plugins folder CPU usage goes to 12.9ms
Expected result: the use of AddComponent should not cause performance spikes with a large codebase
Reproduced in: 2018.1.0a3, 2017.3.0b8, 2017.2.0p1, 2017.1.2p2
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
- Crash on DynamicHeapAllocator::CreateTLSFBlock when opening a specific project
- Scene flickers when using Mesh Output with SpriteLit Shader in 2D project
- “Cache Management” text is misaligned in Preferences > Package Manager
- [macOS] network permission shows the name of previously closed app when different app requests network access
- Delta value returned by mouse movementsMonitor is different when changing Screen Resolution
Resolution Note:
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.