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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Add comment