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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment