Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
0
Found in
2017.3.0b10
2017.3.0f3
Issue ID
1054444
Regression
Yes
Crash on _SimulationFilterShader or PhysicsManager::ProcessTriggerEnterExits when changing meshes during collision
How to reproduce:
1. Open the "Breakable_Crash.zip" project
2. Open the "SimpleCity.unity" scene
3. Enter Play Mode
4. In Scene view Drag ColaMachine game object through Window game object
5. Exit Play Mode
6. Enter Play Mode
7. Repeat step 4
Actual result: Unity crashes. (gif attached)
Reproducible with: 2018.3.0a4, 2018.2.0f2, 2018.1.8f1, 2017.4.7f1, 2017.3.0b10
Regression introduced in: 2017.3.0b10.
Not reproducible with: 2017.3.0b9, 2017.2.3p2.
Note:
After exiting Play Mode first-time error appears: Assertion failed: Assertion failed on expression: 'm_Shape == NULL'
The error and the crash are caused by line: mf.mesh = m; BreakableWindow.cs: 150
-----------------------------------------------------------------
Fixed in 2018.3.0a6, 2018.2.4f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment