Search Issue Tracker
Fixed
Fixed in 1.8.1
Votes
0
Found in [Package]
1.7.3
1.8.0-pre.2
Issue ID
BUR-1985
Regression
Yes
"Invalid allocation label..." errors in the Console when compiling using Burst
Reproduction steps:
- Open the attached project
- Open the “/Assets/Scenes/SingleRobot.unity” Scene
- Enter the Play Mode
- Observe the Console
Expected result: No errors in the Console
Actual result: “Invalid allocation label passed to UnsafeUtility::Free” errors are present in the Console
Reproducible with: 1.6.6, 1.7.3, 1.8.0-pre.2 (2021.3.6f1, 2021.3.8f1)
Not reproducible with: 1.6.6, 1.7.3, 1.8.0-pre.2 (2020.3.39f1)
Couldn’t test with: 2021.1.28f1, 2021.2.19f1, 2021.3.5f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a8 (couldn’t upgrade due to Entities package errors)
Reproducible on: M1 MacOS 12.4 (21F79)
Notes:
- This issue is reproducible on both Apple Silicon and Intel Editors on M1 Mac
- The error goes away when you comment the line 175 in "Packages/com.unity.ai.planner/Runtime/Planner/Jobs/BackpropagationJob.cs"
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