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