Search Issue Tracker
Fixed in 1.3.0-preview.9
Votes
0
Found in [Package]
1.3.0-preview.5
Issue ID
1235201
Regression
No
Crash on invoke_void_FunctionBodyBuilder_Value_Value_uint_bool when trying to inspect a Job in Burst Inspector
Reproduction steps:
1. Open the project attached by the user
2. Define "CRASH_BURST" in Scripting Define Symbols (Edit -> ProjectSettings -> Player -> Scripting Define Symbols)
3. Open Burst Inspector (Jobs -> Burst -> Open Inspector...)
4. In the search field type "MoveInputCancelSystem.ProcessCancels" and select it
Reproducible with: Burst 1.3.0-preview.5 (2019.3.7f1), 1.3.0-preview.8 (2019.3.7f1)
Not reproducible with: Burst 1.3.0-preview.9 (2019.3.7f1, 2019.3.11f1)
First lines of the stacktrace:
at (wrapper managed-to-native) object.wrapper_native_00007FF9BB912120 (Burst.Backend.FunctionBodyBuilder,Burst.Backend.Value,Burst.Backend.Value,uint,bool) [0x00016] in <437ba245d8404784b9fbab9b439ac908>:0
at (wrapper delegate-invoke) <Module>.invoke_void_FunctionBodyBuilder_Value_Value_uint_bool (Burst.Backend.FunctionBodyBuilder,Burst.Backend.Value,Burst.Backend.Value,uint,bool) [0x00069] in <2211e203e83747949c2109f73188f222>:0
at Burst.Backend.StandardCompilerBackend.Store (Burst.Backend.FunctionBodyBuilder,Burst.Backend.Value,Burst.Backend.Value,uint,bool) [0x0000d] in <2211e203e83747949c2109f73188f222>:0
at Burst.Backend.ChainCompilerBackend.Store (Burst.Backend.FunctionBodyBuilder,Burst.Backend.Value,Burst.Backend.Value,uint,bool) [0x0000d] in <2211e203e83747949c2109f73188f222>:0
at Burst.Compiler.IL.Intrinsics.VectorProcessor.TryStoreLocal (Burst.Compiler.IL.Syntax.ILStoreLocal,Burst.Backend.LocalVariable) [0x000c2] in <d44e69c6e62c40a48187c633e22e4133>:0
at Burst.Compiler.IL.ILCompiler.TryIntrinsicStoreLocal (Burst.Compiler.IL.Syntax.ILStoreLocal,Burst.Backend.LocalVariable) [0x00019] in <d44e69c6e62c40a48187c633e22e4133>:0
Notes:
- After upgrading to 1.3.0-preview.9 the issue might reproduce once, but after reopening the project won't reproduce anymore
- The issue seems to be caused by incorrect handling of variable casting to "uint" ((uint)someVariable)
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