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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.3f1