Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
0
Found in
2019.2.0a5
Issue ID
1126175
Regression
Yes
Switching "Version Control" to Perforce throws an error: "SerializedObject target has been destroyed"
Steps to reproduce:
1. Create a new project
2. Go to Project Settings -> Editor
3. Change version control to "Perforce"
Expected result: No errors
Actual result: "SerializedObject target has been destroyed. UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)" error is thrown.
Reproduced in: 2019.2.0a5
Not reproducible in: 2017.4.20f2, 2018.3.5f1, 2019.1.0b3, 2019.2.0a4
Note: Error persists even if you change back "Version Control" to "Hidden Meta Files".
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