Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0b11
2019.1.0a10
Issue ID
1104590
Regression
No
PackedMemorySnapshot: "subSystemList" detected with wrong type
To reproduce:
1) Open user attached project
2) Click Mainmenu > BugReport > Open TestCode Window
3) Click "Capture Memory" button
Actual: The "subSystemList" field is detected as ValueType.
Expected: The "subSystemList" field is detected as Array, which is a ReferenceType.
Reproduced in 2018.3.0b11 and 2019.1.0a10 (subSystemList is not checked in earlier versions)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (2019.1.X):
In mono we initialize class data on access, as such if the member subSystemList's type is never used in the user's code it will not be initialized and therefore skipped by the crawling process. In our case this type is PlayerLoopsystem[], as such any usage of this type either by accessing the aforementioned member or creating a variable of PlayerLoopSystem[] will initialize the type and it will cause the member subSystemsList to be reported(even if it is unused).