Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.3.0f3
Issue ID
983804
Regression
No
ScriptableObject is recognized as MonoBehaviour in the snapshot.nativeTypes array
Reproduction steps:
1. Open the attached project "BugReport_PackedMemorySnapshot_NativeType_ScriptableObject.zip";
2. Select Assets -> New My Scriptable Object in the Main menu;
3. Click BugReport -> Open TestCode Window;
4. Click Capture Memory 'Editor' button;
Expected results: ScriptableObject types should be recognized as ScriptableObject.
Actual results: ScriptableObject is recognized as MonoBehaviour.
Reproduced on: 2018.1.0b1, 2017.3.0p1, 2017.2.1p1, 2017.1.2p4, 5.6.4p3.
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
- 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
Peter77
Jun 23, 2018 07:47
Issue still exists in Unity 2017.4.6f1