Search Issue Tracker
Not Reproducible
Votes
1
Found in
2019.2.0a10
Issue ID
1141506
Regression
Yes
'SerializedObject target has been destroyed" error is shown after switching Asset Pipeline version
Steps to repro:
1. Download the repro project and open it;
2. Go to Project Settings (Edit>Project Settings...);
3. Select Editor tab in the Project Settings window;
4. Expand Mode dropdown list under the Asset Pipeline (experimental) section;
5. Select 'Version 2' in the Mode dropdown list.
Actual result:
`SerializedObject target has been destroyed.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)` error is shown. See attached video.
Expected result:
No errors are shown after switching Asset pipeline version.
Notes:
- On 2019.2.0a14, This bug occurs on selecting any dropdown from Edit > Project Settings > Editor
- Reproducible in 2019.2.0a10;
- In 2019.1.0b9 a different error is shown:
"Failed to load '/Users/vladimir/Documents/Unity Projects/LabsClCrash191/LabsShadowmask/Assets/Scenes/TheLabs_Shadowmask/LightingData.asset' because it was serialized with a newer version of Unity. (Has a higher SerializedFile version)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)"
- Reproducible on OSX 10.14.4 in the attached project and on Windows on the Lighting FTP project from Collab;
- The issue might not reproduce steadily; if it doesn't repro - save the project and restart Editor after switching Asset pipeline version. Then repeat the initial repro steps.
- Another way to repro is to switch Editor visualizations or open Project settings window.
Note:
Also occurring on 2019.2.0a14
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment