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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment