Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
5
Found in
2018.4.25f1
2019.4.3f1
2020.1.0b15
2020.2.0a16
Issue ID
1267271
Regression
Yes
Building a project crashes when a Script Component has serialized array of a type that contains a serialized PropertyName field
How to reproduce:
1. Open the attached project (NamedPropertyBug.zip)
2. Click File -> Build and Run
Expected result: the project builds and runs successfully
Actual result: the Editor crashes without finishing the build
Reproducible with: 2018.4.25f1, 2018.4.26f1, 2019.4.3f1, 2019.4.8f1, 2020.1.0b15, 2020.1.2f1, 2020.2.0a16, 2020.2.0a21
Not reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a15
First lines of the stacktrace:
0x00007FF7BEE5131E (Unity) SerializeTraits<PropertyName>::Transfer<GenerateTypeTreeTransfer>
0x00007FF7C19E8FEA (Unity) Transfer_Blittable_SingleValueField<GenerateTypeTreeTransfer,PropertyName>
0x00007FF7BEE9E7FB (Unity) ExecuteSerializationCommands<ConfigSettingsRead>
0x00007FF7C19EDD0B (Unity) SerializeTraits<ArrayOfManagedObjectsTransferer>::Transfer<GenerateTypeTreeTransfer>
0x00007FF7C19E9807 (Unity) Transfer_ManagedObject<GenerateTypeTreeTransfer,1>
Notes:
the issue doesn't occur when using an array of PropertyName or unserialized fields
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a1
Resolution Note (fix version 2020.1):
Fixed in 2020.1.8f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.28f1