Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
Issue ID
775207
Regression
No
Unity.exe + UnityHelper.exe is fully consuming 3 CPU cores while on login screen
Reproduced in 5.3.3p2
Repro steps:
1. Open up editor
2. Log out of your Unity account
3. Start entering your credentials
4. Observe CPU usage
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment