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.
High CPU usage and slow editor performance while the Profiler with Deep Profiling is on with no complex scripts
Steps to reproduce:
1. Open the user's submitted project
2. Open scene "DebugScene" under Assets/__Test
3. Open the Profiler with enabled Deep Profile and Play the scene
4. As more text will be instantiated, the editor will slow down and the CPU usage in the Deep Profiler will increase
Expected result: Simple script does not severely increase CPU usage in the Deep Profiler
Actual result: Deep Profiler shows CPU usage very high as more text is instantiated
Reproduced with: 5.6.4f1, 2017.1.2p1, 2017.2.0f3, 2017.3.0b4, 2018.1.0a1
Note: Deep Profiling slows down games if complex scripts are running, but in this case the script only instantiates "text"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Gamma bleeding and banding when low light baked in VR scene
- A WebGL build with complex shaders has a performance drop when tapping the screen
- No MipMaps are created when using "UnityWebRequestTexture.GetTexture"
- [Addressables] Crash in TransformParticleMesh
- Canvas Override Sorting breaks sorting order when it is disabled and enabled again