Search Issue Tracker
Fixed in 1.0.1
Votes
0
Found in [Package]
1.0.0
Issue ID
1149347
Regression
No
Unity Burst compiler crashes at "burst_SetCurrentDebugLocation"
Steps to reproduce:
1. Download the attached project and open "Ping" scene
2. Enter play mode
Results: Editor crashes
Reproduced with: 2019.3.0a1, 2019.2.0a12, 2019.1.1f1
Reproduced with Burst package version: 1.0.0, 1.0.0.preview.1
========== OUTPUTTING STACK TRACE ==================
0x00007FFF1498F5B7 (burst-llvm) burst_SetCurrentDebugLocation
0x00007FFF1498F56E (burst-llvm) burst_SetCurrentDebugLocation
0x00007FFF14404ABB (burst-llvm) burst_Return
0x00007FFF1440692D (burst-llvm) burst_ExtractFromAggregate
<...>
========== END OF STACKTRACE ===========
Note:
- Due to package errors in 2018.3 issue wasn't tested in this version.
- In 2019.3.0a1 Editor issue isn't reproducible because of com.unity.transport throws an DllNotFoundException. In Player it is reproducible.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shadows are not cast when the Light's CullingMask and the GameObject's Layer do not match
- Graphics.DrawMeshInstanced does not work when 2D Renderer and 2D Shaders are used
- SpeedTree does not move when using WindZone
- "Undeclared identifier 'LinearToSRGB'" error is thrown when creating a color variable with HDR color mode and assigning a Custom Render Texture target in Shader Graph
- Input System package is missing when creating a new HDRP project
Add comment