Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2018.4
2019.2
2019.3
2019.3.0f3
2020.1
Issue ID
1214853
Regression
No
Unity.Collections.LowLevel.Unsafe.UnsafeUtility.AlignOf<T> always returns 4
How to reproduce:
1. Open tester-attached project (AlignOf.zip)
2. Enter Play Mode
3. See the Console window
Expected result: Unity.Collections.LowLevel.Unsafe.UnsafeUtility.AlignOf<T> returns correct value for the given type T(e.g. 8 for Int64).
Actual result: Unity.Collections.LowLevel.Unsafe.UnsafeUtility.AlignOf<T> always returns 4
Reproducible with: 2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a21
Could not test with: 2017.4.36f1(Unity namespace missing)
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a5
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b6
Resolution Note (fix version 2019.3):
Fixed in 2019.3.11f1