Search Issue Tracker
Fixed in 2017.1.X
Votes
21
Found in
5.5.0p4
Issue ID
878740
Regression
Yes
Crash in physx::PxsBroadPhaseContextSap::batchUpdate after indeterminate time in play mode
Reproduction steps:
1. Open project attached (GoIPhysXCrashRepro.zip)
2. Open scene crashtest1.
3. Press play.
4. Wait for 1-3 minutes.
Expected result: Unity will keep working.
Actual result: Unity crashes.
Notes: It might be related to object creation/destruction but it is not totally clear which kinds of objects will trigger it and which will not.
Reproduced on: 5.5.0f3, 5.5.0p4, 5.5.1p3, 5.6.0b7.
Works fine on: 5.5.0b11.
Regression introduced in: 5.5.0f1
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
cozyurt_unity
Jul 13, 2020 17:28
kedi ve köpek mamaları kedi kumu çeşitleri www.patilimama.com
EastOfEden
Jul 25, 2017 01:34
Same problem.
It is connected to disabling and enabling colliders.
I am using it as a nasty hack to force physics to recognize that the collider is where it is after I move most of the scene to bring the player back to the origin. I will need to change it to some other method - I need a huge map.
Anyway I am sure that this is due to me disabling and enabling the colliders.
5.6.1f1 - this seems to be the latest version available.
hvirtual
Jun 26, 2017 14:13
I have Unity 5.6.1p1 and QA marked the issue I submitted (Case 924500) as a duplicate of this issue.
"YANTMAY 12, 2017 10:25
The fix will be available with 5.6.1p1 that is out in a few days from now. Anthony." - This is not fixed for me.
yant
Jun 01, 2017 13:19
The fix will be available in 5.5, starting 5.5.4p1. Anthony.
Pickyguy
May 30, 2017 00:46
@Yant This issue makes our project very unstable. I can't upgrade to 5.6 right now. Because all assetbundle hashes are updated after upgrade. Every users have to re-download all assets.
Pickyguy
May 30, 2017 00:34
@Yant Do you have any plan to apply this fix for 5.5?
yant
May 15, 2017 11:04
@ AFRISBYMAY - please comment on the cloth-related cases directly. I need to know which ones exactly.
AFrisby
May 12, 2017 16:12
@Yant: will those fixes also cover the other physics crashes, e.g. the ones coming reliably from cloth physics?
yant
May 12, 2017 10:25
The fix will be available with 5.6.1p1 that is out in a few days from now. Anthony.
MarkoDefiant
Apr 28, 2017 03:42
Since the latest round of patches (April 25 & 27) didn't include this fix here's some info that might help out anyone else that is also having this issue;
For us using 5.5.2p2 (or 5.5.2p3) and getting rid of all negative scales on rigidbodies (and their parents) seems to be avoiding this issue. It was a combination of negative scales and reparenting (along with enabling / disabling) that seemed to be the cause of the issue for us.