Search Issue Tracker
Won't Fix
Votes
5
Found in
5.6.0xb8
Issue ID
881375
Regression
No
[Linux Editor] High CPU usage is accumulated on a single core if WebView windows are present
When WebView windows are loaded (Services, Getting Started, etc.), one of computer's cores becomes heavily loaded.
Steps to reproduce:
1) Launch Unity.
2) Monitor CPU usage via 'System Monitor' app.
When Unity is at project selection screen, CPU usage on one of available cores is very high, compared to others (100% on mid-end PC). The high usage alternates between the cores every ~10 seconds. This is most likely caused by the 'Getting Started' section, which is a WebView. When selecting a project to open (Nautilus window takes focus from the project selection window), the CPU usage returns to normal. The same issue occurs when Services or other web windows are open within the Editor.
This does not occur on macOS or Windows.
Reproduced on:
5.2.2f1, 5.3.6f1, 5.6.0b8
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note:
This should be gone once we get rid of libcef, no specific ETA though