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
15
Found in
2017.2.0f3
Issue ID
958676
Regression
No
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"
-
Shadowing
Mar 24, 2018 09:41
Same Issue as well. Profiler is also unusable for me.
Unity 2017.3.1 p1 -
Onsterion
Mar 18, 2018 00:49
Same problem here, extreme slow Editor
Unity Version: 2017.3.1p4
Hardware / Software System:
Sistema operativo
Windows 10 Home 64-bit
CPU
Intel Core i7 7820HK @ 2.90GHz 44 °C
Kaby Lake 14nm Tecnología
RAM
32.0GB Doble-Canal Desconocido @ 1196MHz (17-17-17-39)
Gráfica
Generic PnP Monitor (1920x1080@60Hz)
4095MBNVIDIA GeForce GTX 1070 (MSI) 41 °C
4095MBNVIDIA GeForce GTX 1070 (MSI) 41 °C
versión ForceWare: 391.01
SLI habilitado -
Likewizedog
Dec 01, 2017 13:13
Same issue. Profiler is unusable. Worked fine in 2017.1
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
- The build size is larger when Models have Animation Type set to Generic
Resolution Note (2018.1.X):
This is somewhat expected. In the 17.1 the UI wasn't tracked properly. We are adding more tracking and debugging around the UI. This is what the user is now seeing. The layout performance goes down slowly as its having to determine where each element fits in a grid every time they add more text.