Search Issue Tracker
Fixed in 2021.3.X
Votes
0
Found in
2021.3.0f1
Issue ID
1420651
Regression
Yes
EditorLoop process uses 98% of the Main Thread and causes low FPS and CPU frame time when playing the game
Reproduction steps:
1. Open the attached project
2. Click on the Stats button in the Game View Control Bar
3. Open the Profiler Window (Window > Analysis > Profiler)
4. Enter Play Mode
5. Observe the FPS in the Statistics Window and process EditorLoop total usage in the Profiler Window
Expected result: the EditorLoop process usage should be around 60% and the average FPS should be in the hundreds
Actual result: the EditorLoop process uses about 98% of the Main Thread and FPS tanks to 20
Reproducible with: 2021.3.0f1
Not reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.3f1, 2021.3.4f1, 2022.1.3f1, 2022.2.0a16
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.3f1