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
Comments (1)
-
Felladrin
May 14, 2018 13:33
This issue is still present on version 2018.1.0f2
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note:
This should be gone once we get rid of libcef, no specific ETA though