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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment