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][iOS][UnityPlayerActivity] Legacy InputField.onEndEdit is not called when ending text edit
- Transform corruption and/or crash on PhysX::CreateCharacterController when spawning physics objects into Prefab stages
- UNITY_EDITOR data is Serialized into AssetBundle when building on the active Build Target
- "TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations..." error when changing the Packages "Cache Location" folder
- CompilationPipeline.assemblyCompilationFinished() hangs unity when reloading domain
Add comment