Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2018.3.0b11
2019.1
2019.1.0b10
2019.2
2019.3
Issue ID
1144591
Regression
Yes
"#if UNITY_EDITOR" serialized properties crash Standalone Player when Architecture is x86_64
Reproduction steps:
1. Download "1144591" project
2. Delete the "Library" folder
3. Open the Project
4. Make sure that the TMP Version is '1.4.0' or '2.0.0' (If not, change to those versions and delete the "Library" folder again)
5. Build a Standalone Player (x86_64)
6. Launch the Build
Actual Result: Crash
Fixed in: 2019.3.0a5
Reproduced with: 2019.3.0a2, 2019.2.0a15, 2019.1.1f1, 2018.4.0f1, 2018.3.14f1, 2018.3.0b11
Did not reproduce on: 2018.3.0b10, 2018.2.21f1, 2018.2.0a1, 2018.1.0a1, 2017.4.26f1 (TMP 1.4.0 implemented from 2018.3)
Workaround:
Update TMP
Change the Build Architecture to x86 and then back to x86_64
Note:
Couldn't reproduce largely because of incompatible TMP versions
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions appear when clicking to rename and then deleting the only GameObject in a scene
- Crash on "core::base_hash_set" when using nested [SerializeReference] fields in List<T> structures
- A ghost Game Window and multiple errors appear in the Editor when a Render Texture used by a Camera's "Target Texture" property is deleted
- Color Picker feels less smooth when dragging a Variables Color property in UI Builder Inspector
- Crash on xatlas::internal::pack::Atlas::findChartLocation_bruteForce when generating the lighting
Add comment