Search Issue Tracker
Fixed in 1.15.12
Votes
4
Found in [Package]
2019.4
2020.3
2021.2
2021.2.1f1
2022.1
Issue ID
1378638
Regression
No
Toolbar.paint CPU usage increase when signed in to the Unity account
Reproduction steps:
1. Open the user's attached "Test.zip" project
2. Sign in to Unity account
3. Open Window > Analysis > Profiler
4. Select "Deep profiler"
5. Change Profiler's target to "Editor Mode"
6. Start recording and press any buttons on the keyboard
7. Stop recording and observe Toolbar.paint
8. Sign out of Unity account and repeat 5th and 6th step
Expected result: CPU usage percentage the same after sign out
Actual result: CPU usage percentage is higher when signed in
Reproduced with: 2019.4.34f1, 2020.3.0f1, 2020.3.24f1, 2021.2.7f1, 2022.1.0b2
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
- 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
Resolution Note (fix version 1.15.12):
A fix has been released for this issue in Version Control package v1.14.12/1.15.12.