Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0b7
Issue ID
1003069
Regression
No
Excessively high CPU usage when profiling editor after pausing the game
Steps to reproduce:
1. Open PROJECT_NAME
2. Select the "Application (Main Client)" and make sure that the selected backend is BACKEND_SERVER
3. Play the scene
4. Open profiler, start recording
5. Login and start the "escape"
6. Wait until the game loads, pause it
7. Start profiling the editor
8. Observe the excessively high CPU usage caused by the profiler window
Expected result: after the game is paused and the editor is profiled, commands such as ProfilerWindow.RepaintAllProfilerWindows() should not cause a drastic rise in CPU usage
Reproduced in: 2018.1.0b7
Fixed in: 2018.2.0a4, 2018.1.0b12
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- Decompressing a DeflateStream under IL2CPP misses a few bytes
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Infinite inertial tensor rotation values are not discarded (both AB and RB)
Add comment