Search Issue Tracker
Fixed in 1.0.1
Votes
0
Found in [Package]
1.0.0
Issue ID
1148567
Regression
No
Using a BurstCompile job with latest com.unity.transport package crashes editor
How to reproduce:
1. Open the attached project
2. Enter the Play mode
---Crash---
Reproducible with: 2019.1.1f1, 2019.2.0a12
In 2019.3.0a1 crash is not present but errors are thrown (A Native Collection has not been disposed, resulting in a memory leak.)
Note: Could not test on earlier versions because of the thrown errors
Stack trace:
#0 0x000001523cee7e in llvm::Value::setNameImpl(llvm::Twine const&)
#1 0x000001523cf2de in llvm::Value::setName(llvm::Twine const&)
#2 0x00000151aad80a in llvm::ExtractValueInst::ExtractValueInst(llvm::Value*, llvm::ArrayRef<unsigned int>, llvm::Twine const&, llvm::Instruction*)
#3 0x00000151aac532 in llvm::IRBuilder<llvm::ConstantFolder, llvm::IRBuilderDefaultInserter>::CreateExtractValue(llvm::Value*, llvm::ArrayRef<unsigned int>, llvm::Twine const&)
#4 0x00000151aac4b3 in burst_ExtractFromAggregate
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment