Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
2017.1.0b2
Issue ID
911967
Regression
No
AddComponent<>() high GC usage
Each call of AddComponent<>() function invokes
AttributeHelperEngine::GetParentTypeDisallowingMultipleInclusion and
AttributeHelperEngine::GetRequiredComponents
each method uses MonoType::GetCustomAttributes, which allocates 0.7 KB to GC
How to reproduce:
1. Open attached project
2. Build project for standalone platform
3. Attach profiler to build
4. Spam 'v' in build to call AddComponent<>()
5. Profile the calls
Reproduced on: 5.6.1p1, 2017.1.0b6, 2017.2.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple errors occur when setting the Render Object Event to AfterRenderingPostProcessing while using STP for Upscaling
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
Add comment