Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.13f1
2021.2
2022.1
Issue ID
1349248
Regression
No
GPU dramatically spikes when selecting a GameObject in the Inspector that is referenced in a SerializeField
How to reproduce:
1. Open the user's attached "New Unity testProject.zip" project
2. Open the "SampleScene" Scene
3. Select the "GameObject" GameObject in the Hierarchy window
4. Select the referenced value in the Test Ref property in the Inspector window
Expected result: No GPU spikes occur
Actual result: GPU spikes to 30-50% usage
Reproducible with: 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a6
Note:
- The issue doesn't reproduce with regular types (int, string)
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 (2022.1.X):
It looks like the spike is from the Scene View repainting, which is expected.