Search Issue Tracker
By Design
Votes
0
Found in
2019.3.10f1
2019.3.11f1
2020.1.0b4
2020.2.0a5
Issue ID
1242625
Regression
Yes
Physics.BakeMesh called on the same mesh from multiple threads can lead to a crash
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
Expected result: Editor doesn't crash
Actual result: Editor crashes
Reproducible with: 2019.3.10f1, 2019.3.13f1, 2020.1.0b4, 2020.2.0a5, 2020.2.0a8
Not reproducible with: 2019.3.0a9, 2019.3.9f1, 2020.1.0b3, 2020.2.0a4
Couldn't test with: 2017.4.40f1, 2018.4.22f1, 2019.3.0a8 (Feature wasn't yet introduced)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player
- Lighting data is carried over from one Scene to another when changing Scenes in the Play Mode
- The <sprite> tag inserted image from a Sprite Asset into the UI Builder Button disappears when the Inlined Style Text Shadow Horizontal or Vertical Offset is set to be more than 0 px
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
Resolution Note:
It's undefined behaviour to call BakeMesh() on the same mesh at the same time, the calls can't overlap and the calling code has to guarantee that currently. Updated docs.