Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
13
Found in
2018.3.0a6
2018.4.0f1
2019.1.0a1
2019.1.3f1
2019.2.0a1
2019.3.0a1
Issue ID
1155827
Regression
Yes
Crash on PhysicsScene::ProcessTriggerEnterExits when splitting meshes that also exit a Trigger with OnTriggerExit
How to reproduce:
1. Open attached project
2. Open CrashDemo Scene
3. Enter the Play Mode
Reproducible with: 2018.3.0a6, 2018.4.1f1, 2019.1.3f1, 2019.2.0b2, 2019.3.0a3
Not reproducible with: 2017.4.27f1, 2018.3.0a5
Actual results: crash
Fixed in: 2020.1.0a7
WORKAROUND: The crash happens if a MeshCollider that is currently overlapping with another collider, gets its mesh set to null and then destroyed. Don't reset the sharedMesh to null before destroying meshes that are in the state of overlapping with other objects.
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
- [ChromeOS] Pixelbook can switch to portrait orientations which result in vertical resolution that cannot be undone
- Compute Shader with RWBuffer<> type throws an error when it is compiled with Vulkan API
- [Device Simulator] When simulator window is narrow, toolbar controls deform and some become inacessible
- [Device Simulator] Only one Touch Input is recognized when using Device Simulator
- "PropertiesGUI() is being called recursively" warning produced when trying to open color picker when object picker is opened
mayasarii876
Mar 08, 2022 08:37
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo
thomas-savysoda
Sep 01, 2019 11:03
This is also preventing us from shipping. Hoping this will be fixed soon.
VoodooAssets
Aug 19, 2019 09:01
We were also experiencing a similar bug crash with the same stack trace. In our case however, it was in relation to calling AddComponent<RigidBody> on an object with a MeshCollider not marked Convex. This object would then interact with another trigger in the scene and cause a hard crash in both editor and on device.
koochy_rat
Aug 09, 2019 08:01
Thank you for discovering the workaround! I upgraded from 5.6 and was facing this crash.
JacobK
Jul 01, 2019 23:41
Game breaking bug for my project :(
Can't ship an update until this is fixed