Search Issue Tracker
Won't Fix
Votes
4
Found in [Package]
0.11.0-preview.7
Issue ID
1257950
Regression
Yes
High CPU usage when Entity Debugger Window is open
How to reproduce:
1. Open the attached "Repro.zip" project
2. Open Windows Task Manager -> Notice the CPU usage
3. Open Entity Debugger Window (Windows -> Analysis -> Entity Debugger)
4. Notice the CPU usage again
Expected result: Normal CPU usage (0.1% - 20%)
Actual result: High CPU usage (20% - 80%)
Reproducible with: 2019.4.3f1, 2020.1.0b14, 2020.2.0a17
Reproducible with Entity Package versions: 0.11.0-preview.7, 0.11.1-preview.4
Not reproducible with Entity Package versions: 0.1.1, 0.4.0-preview.10, 0.8.0-preview.8, 0.10.0-preview.6
Notes:
- CPU usage comes back to normal when Entity Debugger Window is closed
- Could not test on 2018.4, because DOTS are not compatible in that stream
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Resolution Note:
The Entity Debugger will be deprecated in the future. It is highly unlikely that this feature will be shipped when Entities comes out of preview. The newer Entities and Systems windows have performance tests tied to them and are much more performant. These windows will take the place of the Entity Debugger.