Search Issue Tracker
Fixed in 2017.1.0f3
Votes
0
Found in
5.5.2f1
Issue ID
895502
Regression
Yes
Unity crashes when multiple joints are created inside the collider with script
Unity crashes when there are multiple game objects with colliders and joints being instantiated in the same place. These game objects' colliders must intersect with another collider already in the scene. Game objects must have two Fixed Joint components, one of them being with connectedBody set to existing RigidBody and other one to null.
Reproduction steps:
1. Open attached project
2. Open scene "base" if it's not already opened
3. Enter play mode
Expected: play mode starts
Actual: Unity crashes
Reproduced on: 5.5.0a6, 5.5.2f1, 5.5.2p4, 5.6.0f3, 2017.1.0a2
Not reproduced on: 5.5.0a5, 2017.1.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on RenderBufferManager::Textures::GetTempBuffer when rendering a specific scene
- The Inspector header is incorrectly displayed when scripts are recompiled while a Scriptable Object instance is selected
- NullReferenceException is thrown when overriding the UxmlObjectReferences in template instances
- Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
Add comment