Search Issue Tracker
Fixed in 1.3.0-preview.11
Votes
0
Found in [Package]
preview.7 - 1.3.0
Issue ID
1225292
Regression
No
BurstRuntime.GetHashCode32 returned hash is inconsistent if called from a different assembly and Burst compilation is enabled
Steps to reproduce:
1. Open the attached project (case_1225292.zip)
2. Under Jobs > Burst, check "Enable Compilation"
3. Open Test Runner (Window > General > Test Runner)
4. Click "Run All"
Expected result: Test succeeds (Hash returned from the natively called method matches the hash called from a different assembly)
Actual result: Test fails (Hash returned from the natively called method does not match the hash returned from a different assembly)
Reproduced in: Burst 1.1.1 (2019.3.6f1), Burst 1.2.3 (2020.1.0b2), Burst preview.7 - 1.3.0 (2020.2.0a3)
Cannot test with: Burst 1.1.0 - preview.4 and older (GetHashCode32 unavailable)
Note: If Burst compilation is disabled, the hashes match
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Add comment