Search Issue Tracker
Fixed
Fixed in 1.8.29
Votes
0
Found in
1.8.28
Issue ID
UUM-135390
Regression
No
Burst compiler uses incorrect method on interface that shares method name and when using generic interface
Steps to reproduce:
1. Open the attached user's project "Burst compiler inconsistancy.zip"
2. Ensure burst compile is disabled (Jobs > Burst > Enable Compilation)
3. Enter play mode and observe the console. It will log "A", "B","C" and "D"
4. Stop play mode and re enable burst compile
5. Enter play mode and observe the console
Actual result: Console logs "A", "A", "C" and "C"
Expected result: Console logs "A", "B","C" and "D"
Reproducible with: Burst 1.6.0 (2022.1.0a1), Burst 1.8.28 (6000.0.68f1, 6000.3.9f1, 6000.4.0b10, 6000.5.0a7)
Environment tested: Windows 11 24H2
Notes:
-The script with the code used is "BurstBug.cs"
-The issue is that the burst compiler will incorrectly compile multiple interfaces with the same method if their methods share the same name and where only one method is used in the instance of using a generic interface where each type has a different implementation of the generic method.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment