Search Issue Tracker
Duplicate
Votes
2
Found in
5.5.0b11
Issue ID
847825
Regression
Yes
[5.5][5.6] Multiple cloth instances cause a crash on scene loading
When loading between scenes, a crash will occur if there are multiple instances of cloth in the unloaded scene.
Reproduction Steps:
1. Build & Run the attached project
2. Press Fire1 (either LMB or Left CTRL) to trigger a reload, repeat until the following message appears (6 times, from my testing):
"PxScene::removeActor(): Actor not assigned to scene or assigned to another scene. Call will be ignored!"
3. Press Fire1 once more, a crash will occur
Alternatively, press Fire2 (RMB or Left ALT) to cause the game to endlessly reload the scene, and it will crash very quickly.
Expected Result:
Unity should not crash when unloading multiple cloth instances.
Reproducible in versions 5.5.0b11 (03364468e96e) and 5.6.0a1 (087280fac800).
Not reproducible in version 5.4.2p3 (466fe82d1f51).
Comments (1)
-
oswin_c
Dec 22, 2016 03:30
I have the same problem, and it is causing a scene I worked hard on to crash upon updating to 5.6.1. Every time I load that scene, Unity fails.
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
- Text is unreadable when DLSS is applied to the Canvas with Render Mode set to World Space
- NullReferenceException errors appear in the Console when changing the values of Visual Effect Control Clip Events' Attributes
- Crash on TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
This is a duplicate of issue #845868