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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment