Search Issue Tracker
Fixed
Votes
0
Found in
5.5.1p2
Issue ID
878565
Regression
Yes
b2Body::SetActive crash caused by specific prefab which has been created on 5.4.4p2 and broken on 5.5.1p2
Steps to reproduce:
1. Open attached project "prefabtest.zip"
2. Open scene SampleScene-Alien-Level1.1
4. Break prefab instance (Gameobject > Break prefab instance)
5. Undo until it hangs (ctrl+z)
0x00000001405A5BB9 (Unity) b2Body::SetActive
0x0000000140DF98AB (Unity) Rigidbody2D::AwakeFromLoad
0x0000000140E50E8A (Unity) AwakeFromLoadQueue::InvokeAwakeFromLoad
0x0000000140E52D8D (Unity) AwakeFromLoadQueue::AwakeFromLoad
0x00000001404A834D (Unity) DirtyAndAwakeFromLoadAfterMerge
Note: The prafab comes from Platformer Pro asset
Reproduced: Crashed when created on 5.4.4p2 and opened on 5.5.1p2
Did not reproduce: Created on 5.4.1f1 opened on 5.5.1p2, created on 5.4.4p2 and opened on 5.6.0b7, created on 5.4.4p2 and opened on 5.5.1p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment